- 16.4.1 Replication Features and Issues
- 16.4.1.1 Replication and AUTO_INCREMENT
- 16.4.1.2 Replication and Character Sets
- 16.4.1.3 Replication of CREATE ... IF NOT EXISTS Statements
- 16.4.1.4 Replication of CREATE TABLE ... SELECT Statements
- 16.4.1.5 Replication with Differing Table Definitions on Master and Slave
- 16.4.1.6 Replication and DIRECTORY Table Options
- 16.4.1.7 Replication of DROP ... IF EXISTS Statements
- 16.4.1.8 Replication of Invoked Features
- 16.4.1.9 Replication with Floating-Point Values
- 16.4.1.10 Replication and FLUSH
- 16.4.1.11 Replication and System Functions
- 16.4.1.12 Replication and LIMIT
- 16.4.1.13 Replication and LOAD DATA INFILE
- 16.4.1.14 Replication and the Slow Query Log
- 16.4.1.15 Replication During a Master Crash
- 16.4.1.16 Replication During a Master Shutdown
- 16.4.1.17 Replication and max_allowed_packet
- 16.4.1.18 Replication with MEMORY Tables
- 16.4.1.19 Replication of the System mysql Database
- 16.4.1.20 Replication and the Query Optimizer
- 16.4.1.21 Replication and Reserved Words
- 16.4.1.22 Slave Errors during Replication
- 16.4.1.23 Replication during a Slave Shutdown
- 16.4.1.24 Replication and Server SQL Mode
- 16.4.1.25 Replication and Temporary Tables
- 16.4.1.26 Replication Retries and Timeouts
- 16.4.1.27 Replication and Time Zones
- 16.4.1.28 Replication and Transactions
- 16.4.1.29 Replication and Triggers
- 16.4.1.30 Replication and TRUNCATE TABLE
- 16.4.1.31 Replication and Variables
- 16.4.1.32 Replication and Views
Statement-based replication of LIMIT clauses
in DELETE,
UPDATE, and
INSERT ...
SELECT statements is unsafe since the order of the
rows affected is not defined. (Such statements can be replicated
correctly with statement-based replication only if they also
contain an ORDER BY clause.) When such a
statement is encountered:
-
When using
STATEMENTmode, a warning that the statement is not safe for statement-based replication is now issued.Currently, when using
STATEMENTmode, warnings are issued for DML statements containingLIMITeven when they also have anORDER BYclause (and so are made deterministic). This is a known issue. (Bug#42851) When using
MIXEDmode, the statement is now automatically replicated using row-based mode.
User Comments
Add your own comment.