jaybird icon indicating copy to clipboard operation
jaybird copied to clipboard

Published 20 hours ago • verified publisher icon FirebirdSQL

Refactor handling of metadata statements/transactions [JDBC465]

Open firebird-automations opened this issue 8 years ago • 4 comments

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 avatar Dec 10 '16 09:12 firebird-automations

Modified by: @mrotteveel

Fix Version: Jaybird 3.1 [ 10441 ]

firebird-automations avatar Dec 10 '16 10:12 firebird-automations

Modified by: @mrotteveel

Link: This issue is related to JDBC464 [ JDBC464 ]

firebird-automations avatar Dec 17 '16 11:12 firebird-automations

Modified by: @mrotteveel

Link: This issue is related to JDBC470 [ JDBC470 ]

firebird-automations avatar Dec 24 '16 18:12 firebird-automations

Modified by: @mrotteveel

Fix Version: Jaybird 5 [ 10871 ]

Fix Version: Jaybird 4 [ 10441 ] =>

firebird-automations avatar Jul 21 '18 11:07 firebird-automations

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 avatar Sep 24 '22 11:09 mrotteveel