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
Some tools (notably ColdFusion) always execute or prepare statements with Statement.RETURN_GENERATED_KEYS (at least: if the database metadata reports support),but as Firebird has limitations in support for RETURNING (only singleton insert/update/delete, otherwise error 335544652 "multiple rows in singleton select" is reported), it might be better to add a connection property that 1) disables generated keys support entirely for a connection, or 2) restricts generated keys support to insert only.
Option 1 could work as a workaround when removing antlr-runtime from the classpath is not an option, and option 2 could be a partial workaround to decrease the chance of the error occurring with tools that execute/prepare all queries with Statement.RETURN_GENERATED_KEYS.
@issush Thanks, I already made some changes with JDBC412 (if there is no antlr-runtime on the classpath), that can be considered a workaround if Cold Fusion checks the database metadata for support.
Submitted by: @mrotteveel
Votes: 1
Some tools (notably ColdFusion) always execute or prepare statements with Statement.RETURN_GENERATED_KEYS (at least: if the database metadata reports support),but as Firebird has limitations in support for RETURNING (only singleton insert/update/delete, otherwise error 335544652 "multiple rows in singleton select" is reported), it might be better to add a connection property that 1) disables generated keys support entirely for a connection, or 2) restricts generated keys support to insert only.
Option 1 could work as a workaround when removing antlr-runtime from the classpath is not an option, and option 2 could be a partial workaround to decrease the chance of the error occurring with tools that execute/prepare all queries with Statement.RETURN_GENERATED_KEYS.
Commits: 9eb0cdc
The text was updated successfully, but these errors were encountered: