mirror of
https://github.com/MariaDB/server.git
synced 2025-01-30 18:41:56 +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.
52 lines
854 B
Text
52 lines
854 B
Text
connect con1,localhost,root,,;
|
|
connect con2,localhost,root,,;
|
|
connection con1;
|
|
SET transaction_isolation = 'READ-COMMITTED';
|
|
CREATE TABLE bug49164 (a INT, b BIGINT, c TINYINT, PRIMARY KEY (a, b))
|
|
ENGINE=InnoDB;
|
|
insert into bug49164 values (1,1,1), (2,2,2), (3,3,3);
|
|
begin;
|
|
update bug49164 set c=7;
|
|
select * from bug49164;
|
|
a b c
|
|
1 1 7
|
|
2 2 7
|
|
3 3 7
|
|
rollback;
|
|
select * from bug49164;
|
|
a b c
|
|
1 1 1
|
|
2 2 2
|
|
3 3 3
|
|
begin;
|
|
update bug49164 set c=7;
|
|
connection con2;
|
|
SET transaction_isolation = 'READ-COMMITTED';
|
|
begin;
|
|
select * from bug49164;
|
|
a b c
|
|
1 1 1
|
|
2 2 2
|
|
3 3 3
|
|
commit;
|
|
begin;
|
|
update bug49164 set c=6 where a=1 and b=1;
|
|
connection con1;
|
|
rollback;
|
|
select * from bug49164;
|
|
a b c
|
|
1 1 1
|
|
2 2 2
|
|
3 3 3
|
|
connection con2;
|
|
commit;
|
|
connection con1;
|
|
select * from bug49164;
|
|
a b c
|
|
1 1 6
|
|
2 2 2
|
|
3 3 3
|
|
connection default;
|
|
disconnect con1;
|
|
disconnect con2;
|
|
drop table bug49164;
|