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

Refactor handling of metadata statements/transactions [JDBC465] #504

Closed
firebird-automations opened this issue Dec 10, 2016 · 5 comments
Closed

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Is related to JDBC464
Is related to JDBC470

As shown in JDBC464 metadata statement handling has some issues. Currently it piggybacks on the active transaction, but maybe it should use its own (read only) transaction instead.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 3.1 [ 10441 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue is related to JDBC464 [ JDBC464 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue is related to JDBC470 [ JDBC470 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 5 [ 10871 ]

Fix Version: Jaybird 4 [ 10441 ] =>

@mrotteveel
Copy link
Member

With the changes in behaviour of READ COMMITTED in Firebird 4.0, using a separate read-only transaction handle for database metadata no longer provides a lot of benefits, but does introduce more overhead (e.g. inhibiting GC), so this is no longer a viable solution.

@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