Bug #28255 | Cursor operations on result sets containing only part of a key are incorrect | ||
---|---|---|---|
Submitted: | 4 May 2007 20:53 | Modified: | 6 Jun 2007 11:56 |
Reporter: | Jim Winstead | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51.15 | OS: | Any |
Assigned to: | Jim Winstead | CPU Architecture: | Any |
Tags: | multipart key, SQLSetPos |
[4 May 2007 20:53]
Jim Winstead
[10 May 2007 18:55]
Jim Winstead
fix building of WHERE clause against a multipart primary key
Attachment: bug28255.patch (application/octet-stream, text), 26.03 KiB.
[10 May 2007 19:19]
Jim Winstead
in addition to fixing the originally-described problem, the attached patch also fixes insert_pk_fields() to handle aliased field names in the result set. it also removes a number of tests that relied upon the old, incorrect, behavior.
[16 May 2007 3:14]
Jim Winstead
Bug #19566 is related to this one. Even with this bug fixed, we sometimes try to use too many fields when there is a suitable primary or unique key available.
[30 May 2007 20:35]
Jim Winstead
The fix for this has been committed to the source repository, and will be in 3.51.16.
[6 Jun 2007 11:56]
MC Brown
A note has been added to the 3.51.16 changelog.