Skip to content
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

Closed
firebird-automations opened this issue Dec 17, 2011 · 8 comments
Closed

Investigate ResultSet behavior in autocommit [JDBC209] #258

firebird-automations opened this issue Dec 17, 2011 · 8 comments

Comments

@firebird-automations
Copy link

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)

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

assignee: Roman Rokytskyy [ rrokytskyy ] => Mark Rotteveel [ avalanche1979 ]

Fix Version: Jaybird 2.3 [ 10440 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC305 [ JDBC305 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC304 [ JDBC304 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC307 [ JDBC307 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC307 [ JDBC307 ] =>

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 3.1 [ 10441 ]

Fix Version: Jaybird 3.0 [ 10440 ] =>

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 5 [ 10871 ]

Fix Version: Jaybird 4 [ 10441 ] =>

@mrotteveel
Copy link
Member

Decided not to change the current behaviour.

@mrotteveel mrotteveel closed this as not planned Won't fix, can't repro, duplicate, stale Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants