New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate ResultSet behavior in autocommit [JDBC209] #258
Comments
Modified by: @mrotteveelassignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ] Fix Version: Jaybird 2.3 [ 10440 ] |
Modified by: @mrotteveel |
Modified by: @mrotteveel |
Modified by: @mrotteveel |
Modified by: @mrotteveel |
Decided not to change the current behaviour. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @mrotteveel
Relate to JDBC305
Relate to JDBC304
The behavior of closing ResultSets in autocommit mode might be too restrictive. Identify current behavior in Jaybird and other drivers, and see if we can/need to change anything in this regard.
See also the discussion "[Firebird-Java] OpenOffice, Jaybird and Embedded Server " on the Firebird-Java list.
and http://stackoverflow.com/questions/935511/how-can-i-avoid-resultset-is-closed-exception-in-java (answer by Sugar)
The text was updated successfully, but these errors were encountered: