mirror of
https://github.com/MariaDB/server.git
synced 2025-01-16 03:52:35 +01:00
d20a96f9c1
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.
24 lines
744 B
Text
24 lines
744 B
Text
# t/unsafe_binlog_innodb.test
|
|
#
|
|
# Note that this test uses at least in case of InnoDB options
|
|
# innodb_locks_unsafe_for_binlog = true
|
|
# innodb_lock_timeout = 5
|
|
#
|
|
# Last update:
|
|
# 2006-08-02 ML test refactored
|
|
# old name was innodb_unsafe_binlog.test
|
|
# main code went into include/unsafe_binlog.inc
|
|
#
|
|
|
|
--source include/have_innodb.inc
|
|
let $engine_type= InnoDB;
|
|
|
|
SET @save_timeout = @@GLOBAL.innodb_lock_wait_timeout;
|
|
SET GLOBAL innodb_lock_wait_timeout = 1;
|
|
SET @save_isolation = @@GLOBAL.transaction_isolation;
|
|
SET GLOBAL TRANSACTION ISOLATION LEVEL READ COMMITTED;
|
|
|
|
--source include/unsafe_binlog.inc
|
|
|
|
SET GLOBAL innodb_lock_wait_timeout = @save_timeout;
|
|
SET GLOBAL transaction_isolation = @save_isolation;
|