SET TRANSACTION statement only has effect until next COMMIT [CORE6111] #6360
Labels
affect-version: 2.1.7
affect-version: 2.5.0
affect-version: 2.5.1
affect-version: 2.5.2 Update 1
affect-version: 2.5.2
affect-version: 2.5.3 Update 1
affect-version: 2.5.3
affect-version: 2.5.4
affect-version: 2.5.5
affect-version: 2.5.6
affect-version: 2.5.7
affect-version: 2.5.8
affect-version: 2.5.9
affect-version: 3.0.0
affect-version: 3.0.1
affect-version: 3.0.2
affect-version: 3.0.3
affect-version: 3.0.4
affect-version: 4.0 Alpha 1
affect-version: 4.0 Beta 1
affect-version: 4.0 Initial
component: isql
priority: major
type: bug
Submitted by: @samofatov
This behavior is happening all the way to Firebird 1.0 builds.
I believe the engine shall preserve transaction isolation mode after commit;
Please correct me if I am wrong.
ISQL commands to reproduce:
SQL>create database '/tmp/test.fdb';
SQL>set transaction read committed;
SQL>select mon$isolation_mode from mon$transactions where mon$transaction_id=current_transaction;
MON$ISOLATION_MODE
SQL> commit;
SQL> select mon$isolation_mode from mon$transactions where mon$transaction_id=current_transaction;
MON$ISOLATION_MODE
The text was updated successfully, but these errors were encountered: