svn commit - mysqldoc@docsrva: r1934 - in trunk: . make.d refman-4.1 refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2006-04-25 17:43:42 +0200 (Tue, 25 Apr 2006)
New Revision: 1934

Log:
 r9732@frost:  paul | 2006-04-25 10:38:09 -0500
 Slight revision regarding ALTER TABLE and consistent read.


Modified:
   trunk/
   trunk/make.d/xml-txt
   trunk/refman-4.1/innodb.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.1/innodb.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6914
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9717
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4590
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6914
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9732
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4590

Modified: trunk/make.d/xml-txt
===================================================================
--- trunk/make.d/xml-txt	2006-04-25 12:21:05 UTC (rev 1933)
+++ trunk/make.d/xml-txt	2006-04-25 15:43:42 UTC (rev 1934)
@@ -35,6 +35,10 @@
 
 # Use standard HTML driver to convert -nolink.xml to HTML
 # (with TOC suppressed), then use lynx to convert HTML to text.
+# The sed command undoes some magic performed in the MYSQL_HTML_XSL
+# stylesheet that keeps bug references and the following URL together
+# on the same line. (They are glued together with "@@", which then
+# is mapped back after text conversion to ": ".)
 
 %.txt: %-nolink.xml %-toc-entries.xml
 	$(XSLTPROC) \

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-04-25 12:21:05 UTC (rev 1933)
+++ trunk/refman-4.1/innodb.xml	2006-04-25 15:43:42 UTC (rev 1934)
@@ -3986,12 +3986,13 @@
         Consistent read does not work over <literal>DROP TABLE</literal>
         because MySQL can't use a table that has been dropped and
         <literal>InnoDB</literal> destroys the table. Consistent read
-        does not work over <literal>ALTER TABLE</literal> because it is
-        executed inside of the transaction that creates a new table and
-        inserts rows from the old table to the new table. When you
-        reissue the consistent read, it will not see any rows in the new
-        table, because they were inserted in a transaction that is not
-        visible in the snapshot read by the consistent read.
+        does not work over <literal>ALTER TABLE</literal> because
+        <literal>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.
       </para>
 
     </section>

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-04-25 12:21:05 UTC (rev 1933)
+++ trunk/refman-5.0/innodb.xml	2006-04-25 15:43:42 UTC (rev 1934)
@@ -3944,12 +3944,13 @@
         Consistent read does not work over <literal>DROP TABLE</literal>
         because MySQL can't use a table that has been dropped and
         <literal>InnoDB</literal> destroys the table. Consistent read
-        does not work over <literal>ALTER TABLE</literal> because it is
-        executed inside of the transaction that creates a new table and
-        inserts rows from the old table to the new table. When you
-        reissue the consistent read, it will not see any rows in the new
-        table, because they were inserted in a transaction that is not
-        visible in the snapshot read by the consistent read.
+        does not work over <literal>ALTER TABLE</literal> because
+        <literal>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.
       </para>
 
     </section>

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-04-25 12:21:05 UTC (rev 1933)
+++ trunk/refman-5.1/innodb.xml	2006-04-25 15:43:42 UTC (rev 1934)
@@ -3912,12 +3912,13 @@
         Consistent read does not work over <literal>DROP TABLE</literal>
         because MySQL can't use a table that has been dropped and
         <literal>InnoDB</literal> destroys the table. Consistent read
-        does not work over <literal>ALTER TABLE</literal> because it is
-        executed inside of the transaction that creates a new table and
-        inserts rows from the old table to the new table. When you
-        reissue the consistent read, it will not see any rows in the new
-        table, because they were inserted in a transaction that is not
-        visible in the snapshot read by the consistent read.
+        does not work over <literal>ALTER TABLE</literal> because
+        <literal>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.
       </para>
 
     </section>