Bug #26973 | MyODBC 5/ADO adDbTime type can't be updated - Regression | ||
---|---|---|---|
Submitted: | 8 Mar 2007 23:08 | Modified: | 2 Dec 2010 8:48 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 5.1.3 | OS: | Windows (win xp) |
Assigned to: | Lawrenty Novitsky | CPU Architecture: | Any |
[8 Mar 2007 23:08]
Erica Moss
[31 Oct 2007 7:31]
Erica Moss
Tested against 3.51.20 and 5.1.0. Problem can't be repeated Added test case to: ado-compliance\trunk\bugs\26973.vbs
[31 Oct 2007 9:25]
Susanne Ebrecht
Hi Eric, This bug is fixed in our new version MyODBC 5.1. I'll close the bug. thank you for trusting MySQL. Kind Regards, Susanne
[12 Apr 2008 3:41]
Erica Moss
trace run against myodbc 5.1.2
Attachment: SQL_512.LOG (application/octet-stream, text), 154.25 KiB.
[12 Apr 2008 3:41]
Erica Moss
trace run against myodbc 5.1.3
Attachment: SQL_513.LOG (application/octet-stream, text), 137.26 KiB.
[12 Apr 2008 6:08]
Erica Moss
This case has been functioning up until MyODBC 5.1.2. As of 5.1.3 an attempt to update a record with a TIME field will cause the cursor to be lost, and the following error returned: -2147467259:Query-based update failed because the row to update could not be found. Test case found in /tests/bugs/26973.vbs
[24 Feb 2010 13:56]
Tonci Grgin
Eric, please reverify if necessary.
[2 Dec 2010 8:48]
Bogdan Degtyariov
The test (ado-compliance\trunk\bugs\26973.vbs) passes without errors in Connector/ODBC 3.51.27 and 5.1.8. Closing the bug