Issue Details (XML | Word | Printable)

Key: JDBC-413
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Add property to disable or restrict generated keys support on connection level

Created: 03/Nov/15 07:46 PM   Updated: 28/Dec/18 01:44 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.2.9
Fix Version/s: Jaybird 4


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
issush added a comment - 24/Oct/16 07:52 AM
Happy to test this with ColdFusion once a fix becomes available

Mark Rotteveel added a comment - 01/Nov/16 12:01 PM
@issush Thanks, I already made some changes with JDBC-412 (if there is no antlr-runtime on the classpath), that can be considered a workaround if Cold Fusion checks the database metadata for support.