Comment 2 for bug 976778

With InnoDB there is still a problem with replication. Consider this case: while "insert into l_themes select ... from themes" is running, another transaction inserts more rows to the themes table and commits before INSERT ... SELECT finishes. So INSERT ... SELECT will not see the rows. But since binlog is a serialized flow of updates, statements inserting more rows into the themes table will be written to binlog before INSERT ... SELECT. So when replaying that log, INSERT ... SELECT _will_ see rows inserted by a previously executed transaction, and different data may be inserted into l_themes.