SET TRANSACTION statement only has effect until next COMMIT
-----------------------------------------------------------
Key: CORE-6111
URL: http://tracker.firebirdsql.org/browse/CORE-6111
Project: Firebird Core
Issue Type: Bug
Components: ISQL
Affects Versions: 2.5.9, 4.0 Beta 1, 3.0.4, 3.0.3, 2.5.8, 4.0 Alpha 1,
3.0.2, 2.5.7, 3.0.1, 2.5.6, 3.0.0, 4.0 Initial, 2.5.5, 2.5.4, 2.5.3 Update 1,
2.1.7, 2.5.3, 2.5.2 Update 1, 2.5.2, 2.5.1, 2.5.0
Reporter: Nickolay 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
==================
3
SQL> commit;
SQL> select mon$isolation_mode from mon$transactions where
mon$transaction_id=current_transaction;
MON$ISOLATION_MODE
==================
1
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
