Author: jstephens
Date: 2010-04-26 15:53:46 +0200 (Mon, 26 Apr 2010)
New Revision: 20237
Log:
BEGIN/COMMIT -> BEGIN ... COMMIT
Modified:
trunk/refman-5.0/replication-notes.xml
trunk/refman-5.1/replication-notes.xml
trunk/refman-5.4/replication-notes.xml
trunk/refman-5.5/replication-notes.xml
trunk/refman-6.0/replication-notes.xml
Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml 2010-04-26 13:51:11 UTC (rev 20236)
+++ trunk/refman-5.0/replication-notes.xml 2010-04-26 13:53:46 UTC (rev 20237)
Changed blocks: 2, Lines Added: 9, Lines Deleted: 8; 1863 bytes
@@ -1480,8 +1480,9 @@
replicate an <literal>InnoDB</literal> master table as a
<literal>MyISAM</literal> slave table. However, if you do this,
there are problems if the slave is stopped in the middle of a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- block because the slave restarts at the beginning of the
+ <literal role="stmt" condition="commit">BEGIN</literal> ...
+ <literal role="stmt">COMMIT</literal> block because the slave
+ restarts at the beginning of the
<literal role="stmt" condition="commit">BEGIN</literal> block.
</para>
@@ -1516,12 +1517,12 @@
<para>
If you update transactional tables from nontransactional tables
- inside a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- sequence, updates to the binary log may be out of synchrony with
- table states if the nontransactional table is updated before the
- transaction commits. This occurs because the transaction is
- written to the binary log only when it is committed.
+ inside a <literal role="stmt" condition="commit">BEGIN</literal>
+ ... <literal role="stmt">COMMIT</literal> sequence, updates to
+ the binary log may be out of synchrony with table states if the
+ nontransactional table is updated before the transaction
+ commits. This occurs because the transaction is written to the
+ binary log only when it is committed.
</para>
<caution>
Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml 2010-04-26 13:51:11 UTC (rev 20236)
+++ trunk/refman-5.1/replication-notes.xml 2010-04-26 13:53:46 UTC (rev 20237)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 931 bytes
@@ -2863,8 +2863,9 @@
replicate an <literal>InnoDB</literal> master table as a
<literal>MyISAM</literal> slave table. However, if you do this,
there are problems if the slave is stopped in the middle of a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- block because the slave restarts at the beginning of the
+ <literal role="stmt" condition="commit">BEGIN</literal> ...
+ <literal role="stmt">COMMIT</literal> block because the slave
+ restarts at the beginning of the
<literal role="stmt" condition="commit">BEGIN</literal> block.
</para>
Modified: trunk/refman-5.4/replication-notes.xml
===================================================================
--- trunk/refman-5.4/replication-notes.xml 2010-04-26 13:51:11 UTC (rev 20236)
+++ trunk/refman-5.4/replication-notes.xml 2010-04-26 13:53:46 UTC (rev 20237)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 931 bytes
@@ -2419,8 +2419,9 @@
replicate an <literal>InnoDB</literal> master table as a
<literal>MyISAM</literal> slave table. However, if you do this,
there are problems if the slave is stopped in the middle of a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- block because the slave restarts at the beginning of the
+ <literal role="stmt" condition="commit">BEGIN</literal> ...
+ <literal role="stmt">COMMIT</literal> block because the slave
+ restarts at the beginning of the
<literal role="stmt" condition="commit">BEGIN</literal> block.
</para>
Modified: trunk/refman-5.5/replication-notes.xml
===================================================================
--- trunk/refman-5.5/replication-notes.xml 2010-04-26 13:51:11 UTC (rev 20236)
+++ trunk/refman-5.5/replication-notes.xml 2010-04-26 13:53:46 UTC (rev 20237)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 931 bytes
@@ -2743,8 +2743,9 @@
replicate an <literal>InnoDB</literal> master table as a
<literal>MyISAM</literal> slave table. However, if you do this,
there are problems if the slave is stopped in the middle of a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- block because the slave restarts at the beginning of the
+ <literal role="stmt" condition="commit">BEGIN</literal> ...
+ <literal role="stmt">COMMIT</literal> block because the slave
+ restarts at the beginning of the
<literal role="stmt" condition="commit">BEGIN</literal> block.
</para>
Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml 2010-04-26 13:51:11 UTC (rev 20236)
+++ trunk/refman-6.0/replication-notes.xml 2010-04-26 13:53:46 UTC (rev 20237)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 931 bytes
@@ -2646,8 +2646,9 @@
replicate an <literal>InnoDB</literal> master table as a
<literal>MyISAM</literal> slave table. However, if you do this,
there are problems if the slave is stopped in the middle of a
- <literal role="stmt" condition="commit">BEGIN</literal>/<literal role="stmt">COMMIT</literal>
- block because the slave restarts at the beginning of the
+ <literal role="stmt" condition="commit">BEGIN</literal> ...
+ <literal role="stmt">COMMIT</literal> block because the slave
+ restarts at the beginning of the
<literal role="stmt" condition="commit">BEGIN</literal> block.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r20237 - in trunk: refman-5.0 refman-5.1 refman-5.4 refman-5.5 refman-6.0 | jon.stephens | 26 Apr |
