17.4.1.28 Replication and Server SQL Mode

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. This advice applies whether you are
using statement-based or row-based replication.

If you are replicating partitioned tables, using different SQL
modes on the master and the slave is likely to cause issues. At
a minimum, this is likely to cause the distribution of data
among partitions to be different in the master's and slave's
copies of a given table. It may also cause inserts into
partitioned tables that succeed on the master to fail on the
slave.

To prepare for these SQL mode changes, it is advisable
before upgrading to read
SQL Mode Changes in MySQL 5.7. That discussion provides
guidelines to assess whether your applications will be affected
by these changes.

The deprecated
ERROR_FOR_DIVISION_BY_ZERO,
NO_ZERO_DATE, and
NO_ZERO_IN_DATE SQL modes are
still recognized so that statements that name them do not
produce an error, but will be removed in a future version of
MySQL. To make advance preparation for versions of MySQL in
which these modes do not exist, applications should be modified
to not refer to those mode names.