summaryrefslogtreecommitdiff
path: root/mysql-test/suite/innodb/t/innodb_bug40360.test
diff options
context:
space:
mode:
authorJunqi Xie <junqi_xie@outlook.com>2023-03-12 13:55:30 +0800
committerDaniel Black <daniel@mariadb.org>2023-04-12 11:04:29 +1000
commitd20a96f9c1c0240eac2ad8520a04f06e218c4e0a (patch)
tree2a9bfbd680ebe5079c29dbf11225d249ea1d490b /mysql-test/suite/innodb/t/innodb_bug40360.test
parent4472a7b4ff79853d931288c1ab8d49bf130e3908 (diff)
downloadmariadb-git-d20a96f9c1c0240eac2ad8520a04f06e218c4e0a.tar.gz
MDEV-21921 Make transaction_isolation and transaction_read_only into system variables
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. The same thing applys for transaction_read_only. MySQL 5.7 solved this problem by making them into system variables. https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-20.html This commit takes a similar approach by adding new system variables and marking the original ones as deprecated. This commit also resolves some legacy problems related to SET STATEMENT and transaction_isolation.
Diffstat (limited to 'mysql-test/suite/innodb/t/innodb_bug40360.test')
-rw-r--r--mysql-test/suite/innodb/t/innodb_bug40360.test2
1 files changed, 1 insertions, 1 deletions
diff --git a/mysql-test/suite/innodb/t/innodb_bug40360.test b/mysql-test/suite/innodb/t/innodb_bug40360.test
index f5187d55092..8e7b309e621 100644
--- a/mysql-test/suite/innodb/t/innodb_bug40360.test
+++ b/mysql-test/suite/innodb/t/innodb_bug40360.test
@@ -5,7 +5,7 @@
-- source include/not_embedded.inc
-SET TX_ISOLATION='READ-COMMITTED';
+SET TRANSACTION_ISOLATION='READ-COMMITTED';
# This is the default since MySQL 5.1.29 SET BINLOG_FORMAT='STATEMENT';