This section discusses how MySQL replicates
TABLE ... SELECT statements.
MySQL 5.7 does not allow a
TABLE ... SELECT statement to make any changes in
tables other than the table that is created by the statement.
Some older versions of MySQL which permitted these statements to
do so; this means that, when using statement-based replication
between a MySQL 5.6 or later slave and a master running a
previous version of MySQL, a
TABLE ... SELECT statement causing changes in other
tables on the master fails on the slave, causing replication to
stop. To keep this from happening, you should use row-based
replication, rewrite the offending statement before running it
on the master, or upgrade the master to MySQL 5.7.
(If you choose to upgrade the master, keep in mind that such a
TABLE ... SELECT statement will fail following the
upgrade unless it is rewritten to remove any side effects on
other tables.) This is not an issue when using row-based
replication, because the statement is logged as a
CREATE TABLE statement with any
changes to table data logged as row-insert events, rather than
as the entire
TABLE ... SELECT.
These behaviors are not dependent on MySQL version:
TABLE ... SELECT always performs an implicit
commit (Section 13.3.3, “Statements That Cause an Implicit Commit”).
If destination table does not exist, logging occurs as
follows. It does not matter whether
EXISTS is present.
format: The statement is logged as written.
ROW format: The statement is logged
statement followed by a series of insert-row events.
If the statement fails, nothing is logged. This includes the
case that the destination table exists and
EXISTS is not given.
When the destination table exists and
EXISTS is given, MySQL 5.7 ignores the
statement completely; nothing is inserted or logged. The
handling of such statements in this regard has changed
considerably in previous MySQL releases; if you are replicating
from a MySQL 5.5.6 or older master to a newer slave, see
CREATE ... IF NOT EXISTS Statements,
for more information.