mirror of
https://github.com/MariaDB/server.git
synced 2025-03-03 01:33:10 +01:00
abb201c131
When using BINLOG statement to execute rows log events, session variables foreign_key_checks and unique_checks are changed temporarily. As each rows log event has their own special session environment and its own foreign_key_checks and unique_checks can be different from current session which executing the BINLOG statement. But these variables are not restored correctly after BINLOG statement. This problem will cause that the following statements fail or generate unexpected data. In this patch, code is added to backup and restore these two variables. So BINLOG statement will not affect current session's variables again. |
||
|---|---|---|
| .. | ||
| binlog.test | ||
| binlog_failure_mixing_engines.test | ||
| binlog_insert_delayed.test | ||
| binlog_truncate.test | ||
| blackhole.test | ||
| ctype_cp932.test | ||
| ctype_cp932_binlog.test | ||
| ctype_ucs_binlog.test | ||
| database.test | ||
| drop_temp_table.test | ||
| innodb_stat.test | ||
| insert_select-binlog.test | ||
| mix_innodb_myisam_binlog.test | ||
| mix_innodb_myisam_side_effects.test | ||