Aún no tenemos significados para "base replication".
1Thus, it's still too early to say anything conclusive about row- based replication.
2Another issue with statement- based replication is that the modifications must be serializable.
3MySQL row- based replication supports this scenario by ignoring the missing columns.
4The storage engine does not allow statement- based replication, for example, the MySQL Cluster engine.
5In theory, row- based replication solves several problems we mention later.
6To handle row- based replication, four new events have been introduced:
7Despite this, there are still some situations that statement- based replication can't currently handle correctly:
8In principle, row- based replication should not suffer from this problem.
9There's no safe way to use temporary tables on the master with statement- based replication.
10The events for handling row- based replication are hard to decode, to say the least.
11So, how do these changes appear in the binary log when using row- based replication?
12This will use the traditional statement- based replication for all statements.
13For row- based replication, you can drop the columns as follows:
14Row- based replication should solve some of these problems, but it's too soon to be sure.
15Statement- based replication has a simple replication model: just execute the same statement on the slave.
16On the other hand, the following event is much cheaper to replicate with statement- based replication: