What will MySQL do to correct the aforementioned limitations?
As of MySQL 5.1.5, you can choose either statement-based replication, or row-based replication. The original replication implement is based on statement-based binary logging. Row-based binary logging resolves the limitations mentioned earlier. For additional information, see Section 6.3, “Row-Based Replication”.
As of MySQL 5.1.5, you can choose either statement-based replication or row-based replication. The original replication implementation is based on statement-based binary logging. Row-based binary logging resolves the limitations mentioned earlier. Beginning with MySQL 5.1.8, mixed replication is also available (by starting the server with –binlog-format=mixed). This hybrid, 「smart」 form of replication 「knows」 whether statement-level replication can safely be used, or row-level replication is required. For additional information, see 項5.1.2. 「レプリケーション フォーマット」.
As of MySQL 5.1.5, you can choose either statement-based replication or row-based replication. The original replication implementation is based on statement-based binary logging. Row-based binary logging resolves the limitations mentioned earlier. Beginning with MySQL 5.1.8, mixed replication is also available (by starting the server with –binlog-format=mixed). This hybrid, “smart” form of replication “knows” whether statement-level replication can safely be used, or row-level replication is required. For additional information, see Section 6.1.2, “Replication Formats”.
