DatabaseMetaData.getBestRowIdentifier handling of 'scope' is wrong [JDBC496] #534
Assignees
Comments
Modified by: @mrotteveelVersion: Jaybird 2.2.13 [ 10805 ] |
Modified by: @mrotteveelFix Version: Jaybird 3.0.1 [ 10831 ] => |
|
Commented by: @mrotteveel The functionality seems to be derived from ODBC, where the expectation is indeed that the bestRowTemporary also considers the wider scopes of transaction and session, and bestRowTransaction also considers session. Fixed implementation, reduced scope for RDB$DB_KEY to transaction in line with getRowIdLifeTime() (although the code itself is prepared for getRowIdLifeTime to also support ROWID_VALID_SESSION) |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @mrotteveel
Currently, the implementation will use the provided scope as the scope of the returned row(s), instead of using it as a filtering condition.
Note that the JDBC apidoc is a bit unclear on how the scope-parameter should be used, but returning the rows with at least the provided scope (or broader) would be a good start.
Commits: 6418236
The text was updated successfully, but these errors were encountered: