Author: shinz
Date: 2006-02-28 17:13:31 +0100 (Tue, 28 Feb 2006)
New Revision: 1459
Log:
binlog_format and mixed replication format won't make it into 5.1.7
Modified:
trunk/refman-5.1/database-administration.xml
trunk/refman-5.1/replication.xml
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-02-28 14:45:30 UTC (rev 1458)
+++ trunk/refman-5.1/database-administration.xml 2006-02-28 16:13:31 UTC (rev 1459)
@@ -3712,8 +3712,8 @@
privilege to set this variable). See
<xref linkend="replication-row-based"/>. The startup
variable was added in MySQL 5.1.5, and the runtime
- variable in MySQL 5.1.7. <literal>MIXED</literal> was
- added in MySQL 5.1.7.
+ variable in MySQL 5.1.8. <literal>MIXED</literal> was
+ added in MySQL 5.1.8.
</para>
<para>
@@ -3761,7 +3761,7 @@
</para>
<para>
- Before MySQL 5.1.7, switching to row-based replication
+ Before MySQL 5.1.8, switching to row-based replication
format would implicitly set
<option>--log-bin-trust-function-creators=1</option> and
<option>--innodb_locks_unsafe_for_binlog</option>. This
Modified: trunk/refman-5.1/replication.xml
===================================================================
--- trunk/refman-5.1/replication.xml 2006-02-28 14:45:30 UTC (rev 1458)
+++ trunk/refman-5.1/replication.xml 2006-02-28 16:13:31 UTC (rev 1459)
@@ -249,7 +249,7 @@
<emphasis>row-based replication</emphasis>. Instead of sending SQL
statements to the slave, the master writes events to its binary
log that indicate how individual table rows are effected. As of
- MySQL 5.1.7, a third option is available: mixed. This will use
+ MySQL 5.1.8, a third option is available: mixed. This will use
statement-based replication by default, and only switch to
row-based replication in particular cases as described below.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1459 - trunk/refman-5.1 | stefan | 28 Feb |
