mirror of
https://github.com/MariaDB/server.git
synced 2025-01-19 13:32:33 +01:00
31c990ca57
Problem: Statements that write to tables with auto_increment columns
based on the selection from another table, may lead to master
and slave going out of sync, as the order in which the rows
are retrieved from the table may differ on master and slave.
Solution: We mark writing to a table with auto_increment table
based on the rows selected from another table as unsafe. This
will cause the execution of such statements to throw a warning
and forces the statement to be logged in ROW if the logging
format is mixed.
Changes:
1. All the statements that writes to a table with auto_increment
column(s) based on the rows fetched from another table, will now
be unsafe.
2. CREATE TABLE with SELECT will now be unsafe.
sql/share/errmsg-utf8.txt:
Added new warning messages.
sql/sql_base.cc:
-Created function to check statements that write to
tables with auto_increment column and has select.
-Marked all the statements that write to a table
with auto_increment column based on rows fetched
from other table(s) as unsafe.
sql/sql_table.cc:
mark CREATE TABLE[with auto_increment column] as unsafe.
12 lines
638 B
Text
12 lines
638 B
Text
#######################################################
|
|
# Wrapper for rpl_multi_update3.test to allow multi #
|
|
# Engines to reuse test code. By JBM 2006-02-15 #
|
|
# Added comments section and to skip when ndb is #
|
|
# Default engine. #
|
|
#######################################################
|
|
--source include/not_ndb_default.inc
|
|
--source include/master-slave.inc
|
|
call mtr.add_suppression('Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT.');
|
|
let $engine_type=MyISAM;
|
|
-- source extra/rpl_tests/rpl_multi_update3.test
|
|
--source include/rpl_end.inc
|