[+/-]
AUTO_INCREMENTDIRECTORY Table OptionsFLUSHLIMITLOAD OperationsMEMORY TablesThe following sections provide information about what is supported and what is not in MySQL replication, and about specific issues and situations that may occur when replicating certain statements.
In general, replication compatibility at the SQL level requires
that any features used be supported by both the master and the
slave servers. If you use a feature on a master server that is
available only as of a given version of MySQL, you cannot
replicate to a slave that is older than that version. Such
incompatibilities are likely to occur between series, so that, for
example, you cannot replicate from MySQL 4.1 to
4.0. However, these incompatibilities also can occur
for within-series replication. For example, the
CONVERT_TZ() function is available
in MySQL 4.1.3 and up. If you use this function on the master
server, you cannot replicate to a slave server that is older than
MySQL 4.1.3.
Additional information specific to InnoDB and
replication is given in
Section 13.2.5.5, “InnoDB and MySQL Replication”.

User Comments
I use deleting requests from slave in one of my projects to save requests history on master. So I noticed that INSERT IGNORE query with affected rows 0 wouldn't be replicated.
So if you want to get asynchronous data on slave use INSERT ON DUPLICATE KEY UPDATE or REPLACE.
Add your own comment.