Bug #53235 | SQLColumns returns wrong transfer octet length and display size for DECIMAL | ||
---|---|---|---|
Submitted: | 28 Apr 2010 6:29 | Modified: | 30 Jun 2010 9:35 |
Reporter: | Bogdan Degtyariov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 5.1.6 | OS: | Any |
Assigned to: | Bogdan Degtyariov | CPU Architecture: | Any |
Tags: | decimal, SQLColumns, TRANSFER OCTET LENGTH |
[28 Apr 2010 6:29]
Bogdan Degtyariov
[28 Apr 2010 10:54]
Bogdan Degtyariov
patch
Attachment: bug53235.diff (text/x-diff), 2.77 KiB.
[28 Apr 2010 14:48]
Lawrenty Novitsky
Bogdan, looks like you changed column size too. But according to http://msdn.microsoft.com/en-us/library/ms711786(v=VS.85).aspx columns size unlike transfer octet length should be 10 for decimal(10,3) Thus half of patch seems to be incorrect. The rest - BUFFER_LENGTH part, looks fine.
[29 Apr 2010 8:34]
Bogdan Degtyariov
patch v2
Attachment: bug53235v2.diff (text/x-diff), 1.91 KiB.
[21 May 2010 7:52]
Lawrenty Novitsky
Patch has been pushed to the trunk as rev#896 and has good chances to be included in the next(after 5.1.6) release
[24 May 2010 10:36]
Tony Bedford
An entry has been added to the 5.1.7 changelog: The SQLColumns function returned the incorrect transfer octet length and display size for DECIMAL type.
[30 Jun 2010 9:35]
Tony Bedford
Updated the changelog: The SQLColumns function returned the incorrect transfer octet length into the column BUFFER_LENGTH for DECIMAL type.