Issue Details (XML | Word | Printable)

Key: JDBC-305
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0

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

Holdable ResultSet is closed on autocommit

Created: 30/Mar/13 07:52 AM   Updated: 11/May/13 03:13 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.1.6, Jaybird 2.2, Jaybird 2.2.1, Jaybird 2.2.2
Fix Version/s: Jaybird 2.2.3, Jaybird 3.0.0

Issue Links:

 Description  « Hide
A holdable ResultSet is closed on commit (during autocommit), it should remain open. This is related to JDBC-304 where in 2.2.x no rows can be retrieved from a holdable ResultSet after commit.

The logic surrounding statement completion, commits etc in the driver spreads responsibility around too much (eg the transaction coordinator needs to know what happens with statements, Statement needs to know what should happen with the ResultSet and vice versa). This may need to be reworked in an observer pattern to decouple this.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 30/Mar/13 07:53 AM
Tentatively scheduled for 2.2.3, may need to defer some work to 2.3 as it is not a good idea to tear up the existing structure in a point release.

Mark Rotteveel added a comment - 30/Mar/13 03:41 PM
Changes made for JDBC-304 fix this problem. More radical changes will be done as part of JDBC-307 for Jaybird 2.3