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