Bug #26652 | MyODBC / ADO Set data type is failing to update | ||
---|---|---|---|
Submitted: | 26 Feb 2007 23:24 | Modified: | 2 Jan 2008 22:58 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 5.1 | OS: | Windows (win xp) |
Assigned to: | CPU Architecture: | Any |
[26 Feb 2007 23:24]
Erica Moss
[26 Feb 2007 23:24]
Erica Moss
data file
Attachment: setTest.csv (application/vnd.ms-excel, text), 442 bytes.
[26 Feb 2007 23:25]
Erica Moss
script unit test fle
Attachment: setbug.vbs (application/octet-stream, text), 3.61 KiB.
[27 Feb 2007 7:29]
Erica Moss
Additional information: With the 3.51 drivers it was found that if you add a primary key column to the data set, and make the necessary adjustments to the script, then the test will pass. However making these changes does not alter the results when run against the 5.0 drivers. Excerpt from the mysql general log when the first update attempt is made: 226 Connect root@localhost on ado 226 Query SET NAMES utf8 226 Query SELECT database() 226 Query SELECT database() 226 Query SELECT * FROM set_test 227 Connect root@localhost on ado 227 Query SET NAMES utf8 227 Quit 228 Connect root@localhost on ado 228 Query SET NAMES utf8 228 Quit 070227 1:26:25 226 Quit
[31 Oct 2007 21:31]
Erica Moss
Can't repeat this problem against 3.51.20. This can't be tested against 5.1 until bug #26985 is resolved. Testcase added to the script unit framework: ado-compliance\trunk\bugs\26652.vbs
[2 Jan 2008 22:58]
Jess Balint
ADO test case passes against ODBC 5.1 svn r975 (5.1.2-dev)