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

Develop cleaner solution for closing resources on commit/rollback [JDBC401] #442

Open
firebird-automations opened this issue Jul 11, 2015 · 5 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Is related to JDBC307

The fix for JDBC307 goes through a number of layers to not close the serverside cursor on commit/rollback (as this is done automatically by Firebird). It might be worthwhile to investigate an alternative solution, where the signalling of commiting or rolling back will make those resources (result set, but also blobs) switch to closed state without calling the server side.

This would probably be cleaner and less confusing.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue is related to JDBC307 [ JDBC307 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 3.0 [ 10440 ]

@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

Deferring for later release. Not a priority.

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