mirror of
https://github.com/MariaDB/server.git
synced 2025-01-20 22:12:30 +01:00
19c380aaff
Non-transactional updates that take place inside a transaction present problems for logging because they are visible to other clients before the transaction is committed, and they are not rolled back even if the transaction is rolled back. It is not always possible to log correctly in statement format when both transactional and non-transactional tables are used in the same transaction. In the current patch, we ensure that such scenario is completely safe under the ROW and MIXED modes.
27 lines
827 B
Text
27 lines
827 B
Text
drop table if exists t1,t2;
|
|
create table t1(a int, unique(a));
|
|
insert into t1 values(2);
|
|
create table t2(a int);
|
|
insert into t2 values(1),(2);
|
|
reset master;
|
|
insert into t1 select * from t2;
|
|
ERROR 23000: Duplicate entry '2' for key 'a'
|
|
show binlog events from <binlog_start>;
|
|
Log_name Pos Event_type Server_id End_log_pos Info
|
|
master-bin.000001 # Query # # BEGIN
|
|
master-bin.000001 # Table_map # # table_id: # (test.t1)
|
|
master-bin.000001 # Write_rows # # table_id: # flags: STMT_END_F
|
|
master-bin.000001 # Query # # COMMIT
|
|
select * from t1;
|
|
a
|
|
1
|
|
2
|
|
drop table t1, t2;
|
|
create table t1(a int);
|
|
insert into t1 values(1),(1);
|
|
reset master;
|
|
create table t2(unique(a)) select a from t1;
|
|
ERROR 23000: Duplicate entry '1' for key 'a'
|
|
show binlog events from <binlog_start>;
|
|
Log_name Pos Event_type Server_id End_log_pos Info
|
|
drop table t1;
|