Bug #29883 | MyODBC 3/ADO recordset update if SQL includes a Limit clause | ||
---|---|---|---|
Submitted: | 18 Jul 2007 23:48 | Modified: | 6 Feb 2008 4:48 |
Reporter: | Erica Moss | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.17 | OS: | Windows (xp sp 2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[18 Jul 2007 23:48]
Erica Moss
[18 Jul 2007 23:49]
Erica Moss
SQL with limit client cursor
Attachment: SQL with limit client cursor.LOG (application/octet-stream, text), 66.25 KiB.
[18 Jul 2007 23:50]
Erica Moss
SQL with limit server cursor
Attachment: SQL with limit server cursor.LOG (application/octet-stream, text), 63.84 KiB.
[18 Jul 2007 23:50]
Erica Moss
SQL without limit
Attachment: SQL without limit.LOG (application/octet-stream, text), 64.22 KiB.
[2 Feb 2008 4:03]
Jess Balint
This works fine in both 3.51 and 5.1. The following update is issued: 980 Query UPDATE `ado_test` SET `c3`=123 WHERE `C1`=1 LIMIT 1 Please add ADO regression test.
[6 Feb 2008 3:16]
Erica Moss
Tested against 3.51.23 = problem still exists "Trace: 3219::Operation is not allowed in this context." Test case added to ADO Conformance tests /bugs/29883.vbs ODBC trace added for the server side test case from trace: "UPDATE `ado`..`29883` SET C3=? WHERE (C1=? AND C2=? AND C3=? )"
[6 Feb 2008 3:17]
Erica Moss
new odbc trace 3.51.23
Attachment: SQL.LOG (application/octet-stream, text), 107.33 KiB.
[6 Feb 2008 4:48]
Jess Balint
This is a duplicate of bug#27351.