Bug #68014 [Opn]: Result data values can be truncated because of incorrect column display sizes
| From: | marcus dot england at noaa dot gov | Date: | Wed, 17 Sep 2014 14:34:52 +0000 |
| Subject: | Bug #68014 [Opn]: Result data values can be truncated because of incorrect column display sizes | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-187567@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=68014&edit=1
ID: 68014
User updated by: marcus dot england at noaa dot gov
Reported by: marcus dot england at noaa dot gov
Summary: Result data values can be truncated because of
incorrect column display sizes
Status: Open
Type: Bug
Package: ODBC related
Operating System: All
-PHP Version: 5.4.32
+PHP Version: >= 5.4.32
Block user comment: N
Private report: N
New Comment:
Introduced in version 5.4.32...
Previous Comments:
------------------------------------------------------------------------
[2014-09-12 20:16:41] marcus dot england at noaa dot gov
Description:
------------
The FieldIdentifier is being incorrectly set in the call to SQLColAttributes within the
odbc_bindcols function in the ext/odbc/php_odbc.c file. Bug was introduced in version 5.4.32 and is
present in all subsequent versions.
In the column FOR loop, if the field identifier variable (colfieldid) is changed from
SQL_COLUMN_DISPLAY_SIZE to SQL_DESC_OCTET_LENGTH for a SQL_CHAR, SQL_VARCHAR, SQL_WCHAR, or
SQL_WVARCHAR column type, it will remain that way for any remaining columns in the table regardless
of type.
This causes SQLColAttributes to be called with the wrong identifier which returns an incorrect
display size. In the case of a table with TINYINTs, this causes the displaysize to be incorrectly
set to 1 rather than 3, resulting in too little memory being allocated for the result value,
truncating the data.
Test script:
---------------
I tested with a table of tinyint's and varchar(20)'s with SQL Server and FreeTDS. tinyint
columns that follow a varchar are incorrectly set to displaysize of 1 resulting in a truncation of
the data, e.g. 85 becomes an 8. The displaysize should be 3.
Expected result:
----------------
If we reset the FieldIdentifier to SQL_COLUMN_DISPLAY_SIZE for each iteration of the column loop,
the bug is fixed.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=68014&edit=1