svn commit - mysqldoc@docsrva: r22791 - trunk/refman-5.1

[john.russell]

Author: jrussell
Date: 2010-09-21 01:12:38 +0200 (Tue, 21 Sep 2010)
New Revision: 22791

Log:
Minor editorial changes for "Consistent Nonlocking Reads".


Modified:
   trunk/refman-5.1/se-innodb-core.xml


Modified: trunk/refman-5.1/se-innodb-core.xml
===================================================================
--- trunk/refman-5.1/se-innodb-core.xml	2010-09-20 23:12:25 UTC (rev 22790)
+++ trunk/refman-5.1/se-innodb-core.xml	2010-09-20 23:12:38 UTC (rev 22791)
Changed blocks: 4, Lines Added: 13, Lines Deleted: 16; 2888 bytes

@@ -6203,11 +6203,11 @@
         to this rule is that the query sees the changes made by earlier
         statements within the same transaction. This exception causes
         the following anomaly: If you update some rows in a table, a
-        <literal role="stmt">SELECT</literal> will see the latest
-        version of the updated rows, but it might also see older
-        versions of any rows. If other sessions simultaneously update
-        the same table, the anomaly means that you may see the table in
-        a state that never existed in the database.
+        <literal role="stmt">SELECT</literal> sees the latest version of
+        the updated rows, but it might also see older versions of any
+        rows. If other sessions simultaneously update the same table,
+        the anomaly means that you might see the table in a state that
+        never existed in the database.
       </para>
 
       <para>

@@ -6312,9 +6312,7 @@
       </para>
 
       <para>
-        Consistent read does not work over <literal role="stmt">DROP
-        TABLE</literal> or over <literal role="stmt">ALTER
-        TABLE</literal>:
+        Consistent read does not work over certain DDL statements:
       </para>
 
       <itemizedlist>

@@ -6322,7 +6320,7 @@
         <listitem>
           <para>
             Consistent read does not work over <literal role="stmt">DROP
-            TABLE</literal> because MySQL cannot use a table that has
+            TABLE</literal>, because MySQL cannot use a table that has
             been dropped and <literal>InnoDB</literal> destroys the
             table.
           </para>

@@ -6331,13 +6329,12 @@
         <listitem>
           <para>
             Consistent read does not work over
-            <literal role="stmt">ALTER TABLE</literal> because
-            <literal role="stmt">ALTER TABLE</literal> works by making a
-            temporary copy of the original table and deleting the
-            original table when the temporary copy is built. When you
-            reissue a consistent read within a transaction, rows in the
-            new table are not visible because those rows did not exist
-            when the transaction's snapshot was taken.
+            <literal role="stmt">ALTER TABLE</literal>, because that
+            statement makes a temporary copy of the original table and
+            deletes the original table when the temporary copy is built.
+            When you reissue a consistent read within a transaction,
+            rows in the new table are not visible because those rows did
+            not exist when the transaction's snapshot was taken.
           </para>
         </listitem>