mirror of
https://github.com/MariaDB/server.git
synced 2025-01-27 09:14:17 +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.
27 lines
972 B
Text
27 lines
972 B
Text
# t/concurrent_innodb_unsafelog.test
|
|
#
|
|
# Concurrent InnoDB tests
|
|
#
|
|
# Last update:
|
|
# 2006-07-26 ML test refactored (MySQL 5.1)
|
|
# main code t/innodb_concurrent.test -> include/concurrent.inc
|
|
# new wrapper t/concurrent_innodb.test
|
|
# 2008-06-03 KP test refactored; removed name locks, added comments.
|
|
# renamed wrapper t/concurrent_innodb.test ->
|
|
# t/concurrent_innodb_unsafelog.test
|
|
# new wrapper t/concurrent_innodb_safelog.test
|
|
#
|
|
|
|
--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;
|
|
--disable_service_connection
|
|
--source include/concurrent.inc
|
|
--enable_service_connection
|
|
SET GLOBAL innodb_lock_wait_timeout = @save_timeout;
|
|
SET GLOBAL transaction_isolation = @save_isolation;
|