Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
Description
In MariaDB, we have a confusing problem where:
- The transaction_isolation option can be set in a configuration file, but it cannot be set dynamically.
- The tx_isolation system variable can be set dynamically, but it cannot be set in a configuration file.
Therefore, we have two different names for the same thing in different contexts. This is needlessly confusing, and it complicates the documentation.
MySQL 5.7 solved this problem by making transaction_isolation into a system variable:
https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_transaction_isolation
Same has been done to transaction_read_only option:
https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html
Attachments
Issue Links
- causes
-
MDEV-31746 Problems with tx_isolation after MDEV-21921
- Closed
- is part of
-
MDEV-28906 MySQL 8.0 desired compatibility
- Open
- relates to
-
CONJ-1087 handle mariadb-11.1+ transaction_isolation
- Closed
-
MDEV-23520 Unknown system variable 'transaction_isolation'
- Closed
-
MDEV-31576 Unknown system variable 'transaction_isolation'
- Closed
-
MDEV-32109 Compatibility Broken with Mysql JDBC Connector
- Closed
- links to