MySQL 5.0 Reference Manual :: 16 Replication :: 16.4 Replication Notes and Tips :: 16.4.1 Replication Features and Issues :: 16.4.1.20 Replication and Server SQL Mode
Section Navigation [Toggle]
- 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 TABLE ... SELECT Statements
- 16.4.1.4 Replication and DIRECTORY Table Options
- 16.4.1.5 Replication of DROP ... IF EXISTS Statements
- 16.4.1.6 Replication with Floating-Point Values
- 16.4.1.7 Replication and FLUSH
- 16.4.1.8 Replication and System Functions
- 16.4.1.9 Replication and LIMIT
- 16.4.1.10 Replication and LOAD Operations
- 16.4.1.11 Replication and the Slow Query Log
- 16.4.1.12 Replication During a Master Crash
- 16.4.1.13 Replication During a Master Shutdown
- 16.4.1.14 Replication with MEMORY Tables
- 16.4.1.15 Replication of the System mysql Database
- 16.4.1.16 Replication and the Query Optimizer
- 16.4.1.17 Replication and Reserved Words
- 16.4.1.18 Slave Errors during Replication
- 16.4.1.19 Replication during a Slave Shutdown
- 16.4.1.20 Replication and Server SQL Mode
- 16.4.1.21 Replication and Temporary Tables
- 16.4.1.22 Replication Retries and Timeouts
- 16.4.1.23 Replication and Time Zones
- 16.4.1.24 Replication and Transactions
- 16.4.1.25 Replication and Triggers
- 16.4.1.26 Replication and User Privileges
- 16.4.1.27 Replication and Variables
- 16.4.1.28 Replication and Views
Using different server SQL mode settings on the master and the
slave may cause the same INSERT
statements to be handled differently on the master and the
slave, leading the master and slave to diverge. For best
results, you should always use the same server SQL mode on the
master and on the slave.
For more information, see Section 5.1.7, “Server SQL Modes”.
User Comments
Add your own comment.