Bug #65738 [Opn->Nab]: Column metadata for datetimeoffset is incorrect

Edit report at https://bugs.php.net/bug.php?id=65738&edit=1 ID: 65738 Updated by: adambaratz@php.net Reported by: chriskl@php.net Summary: Column metadata for datetimeoffset is incorrect -Status: Open +Status: Not a bug Type: Bug Package: PDO DBlib Operating System: Debian 7.1 PHP Version: 5.5.4 Block user comment: N Private report: N New Comment: I'm guessing you saw this because of the TDS version you used. This column type was introduced in SQL Server 2008, so you have use TDS >=7.3. You can choose the TDS version with a "version" param in the DSN. Some general compatibility notes: https://technet.microsoft.com/en-us/library/ms180878(v=sql.105).aspx#Backward Compatibility for Down-level Clients http://www.freetds.org/userguide/choosingtdsprotocol.htm Previous Comments: ------------------------------------------------------------------------ [2013-09-23 02:56:11] chriskl@php.net Actually, unfortunately on a real char field, it also returns "char" and also type 47 :( So I'm not sure how to distinguish these. ------------------------------------------------------------------------ [2013-09-23 02:53:43] chriskl@php.net Description: ------------ When using getColumnMeta() on pdo_dblib, on a column of type 'datetimeoffset(0)', the returned structure looks like this: array(10) { ["max_length"] => int(104) ["precision"] => int(0) ["scale"] => int(0) ["column_source"] => string(7) "updated" ["native_type"] => string(4) "char" ["native_type_id"] => int(47) ["native_usertype_id"] => int(0) ["name"] => string(7) "updated" ["len"] => int(104) ["pdo_type"] => int(2) } Note that it believes that the native_type is char, when it should be 'datetimeoffset'. Expected result: ---------------- I expect to see 'datetimeoffset' as the native_type. Actual result: -------------- You get 'char' - which is incorrect. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=65738&edit=1