Bug #34330 | MyODBC 3 and 5/ ADO Unable to write to a Bit(>1) field | ||
---|---|---|---|
Submitted: | 5 Feb 2008 19:46 | ||
Reporter: | Erica Moss | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51.23 | OS: | Windows (XP sp2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[5 Feb 2008 19:46]
Erica Moss
[5 Feb 2008 19:54]
Erica Moss
In the case of 3.51.23 both client and server fail. In the case of 5.1.1 server passes, client fails Test case added to ado_conformance tests /bugs/34330.vbs attaching traces for both drivers
[5 Feb 2008 19:57]
Erica Moss
5.1.1 driver trace
Attachment: SQL_511_driver.LOG (application/octet-stream, text), 202.31 KiB.
[5 Feb 2008 20:01]
Erica Moss
3.51.23 driver trace, server side cursor test
Attachment: SQL_351_driver.LOG (application/octet-stream, text), 152.22 KiB.
[20 Oct 2008 19:55]
Jess Balint
Delayed pending fix of bug#40187
[10 Oct 2010 14:12]
Lawrenty Novitsky
taking not assigned bugs. perhaps this bug is fixed in 5.1
[3 Dec 2010 8:19]
Bogdan Degtyariov
Updating BIT field failed with MyODBC 5.1.8. However, the problem seems to be different this time: Microsoft Cursor Engine: Row cannot be located for updating. Some values may have been changed since it was last read IMO this error is connected to bug #30349.