You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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: