Updatable resultsets without primary key do not work in Firebird 3 [JDBC330] #376
Comments
Modified by: @mrotteveel |
Modified by: @mrotteveeldescription: See CORE4255. A workaround was added to FBRowUpdater in 2.2.4. This issue serves as a reminder that it needs to be removed when CORE4255 gets fixed in the next Firebird 3 alpha or beta. => See CORE4255. A workaround was added to FBRowUpdater.appendWhereClause(..) in 2.2.4. This issue serves as a reminder that it needs to be removed when CORE4255 gets fixed in the next Firebird 3 alpha or beta. |
Modified by: @mrotteveelFix Version: Jaybird 2.2.5 [ 10582 ] |
|
Commented by: @mrotteveel Before 2.2.4 release, move the cast from RDB$DB_KEY to the parameter, it will probably be better for performance. |
|
Commented by: @mrotteveel Made change in 2.2.4 to cast parameter instead. Actual problem has been fixed (since build 30717). Waiting for release of Alpha 2 to revert this workaround. |
Modified by: @mrotteveelFix Version: Jaybird 2.2.6 [ 10588 ] Fix Version: Jaybird 2.2.5 [ 10582 ] => |
|
Commented by: @mrotteveel Reverted workaround for 2.2.6 |
Modified by: @mrotteveelVersion: Jaybird 2.2.5 [ 10582 ] |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
firebird-issue-importer
added
affect-version: Jaybird 2.2.3
affect-version: Jaybird 2.2.2
affect-version: Jaybird 2.2.1
affect-version: Jaybird 2.2
affect-version: Jaybird 2.1.6
affect-version: Jaybird 2.2.4
affect-version: Jaybird 2.2.5
fix-version: Jaybird 2.2.6
resolution: fixed
priority: major
component: jni/jna layer
component: wire protocol
type: bug
labels
Submitted by: @mrotteveel
Depends on CORE4255
See CORE4255. A workaround was added to FBRowUpdater.appendWhereClause(..) in 2.2.4.
This issue serves as a reminder that it needs to be removed when CORE4255 gets fixed in the next Firebird 3 alpha or beta.
Commits: 989bb22 5dd81d5 b147a66 d38d886 FirebirdSQL/fbt-repository@3dc1cc0 FirebirdSQL/fbt-repository@0462930 FirebirdSQL/fbt-repository@3574e35 FirebirdSQL/fbt-repository@184e947
The text was updated successfully, but these errors were encountered: