svn commit - mysqldoc@oter02: r26662 - trunk/dynamic-docs/changelog

[jon.stephens]

Author: js221926
Date: 2011-06-30 19:32:50 +0200 (Thu, 30 Jun 2011)
New Revision: 26662

Log:

Add/improve auto-link markup



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld-2.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2011-06-30 17:11:54 UTC (rev 26661)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2011-06-30 17:32:50 UTC (rev 26662)
Changed blocks: 4, Lines Added: 12, Lines Deleted: 9; 2157 bytes

@@ -1816,9 +1816,10 @@
         <literal>TRUNCATE PARTITION</literal>, makes it possible to
         delete rows from one or more selected partitions only. Unlike
         the case with <literal>ALTER TABLE ... DROP PARTITION</literal>,
-        <literal>ALTER TABLE ... TRUNCATE PARTITION</literal> merely
-        deletes all rows from the specified partition or partitions, and
-        does not change the definition of the table.
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE ... TRUNCATE PARTITION</literal> merely deletes all rows
+        from the specified partition or partitions, and does not change
+        the definition of the table.
       </para>
 
     </message>

@@ -1845,8 +1846,9 @@
         <literal>PARTITION BY LIST
         COLUMNS(<replaceable>column_list</replaceable>)</literal>
         options are added for the <literal role="stmt">CREATE
-        TABLE</literal> and <literal role="stmt">ALTER TABLE</literal>
-        statements.
+        TABLE</literal> and
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE</literal> statements.
       </para>
 
       <para>

@@ -5069,8 +5071,9 @@
     <message>
 
       <para>
-        <literal role="stmt">ALTER TABLE</literal> on a partitioned
-        table caused unnecessary deadlocks.
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE</literal> on a partitioned table caused unnecessary
+        deadlocks.
       </para>
 
     </message>

@@ -6083,8 +6086,8 @@
 
       <para>
         Running an <literal role="stmt">ALTER TABLE</literal> statement
-        while an NDB backup was in progress caused
-        <command>mysqld</command> to crash.
+        while an <literal role="se">NDB</literal> backup was in progress
+        caused <command>mysqld</command> to crash.
       </para>
 
     </message>


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2011-06-30 17:11:54 UTC (rev 26661)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2011-06-30 17:32:50 UTC (rev 26662)
Changed blocks: 4, Lines Added: 24, Lines Deleted: 19; 3558 bytes

@@ -6814,9 +6814,11 @@
     <message>
 
       <para>
-        An <literal role="stmt">ALTER TABLE</literal> statement acting
-        on table partitions that failed while the affected table was
-        locked could cause the server to crash.
+        An
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE</literal> statement acting on table partitions that failed
+        while the affected table was locked could cause the server to
+        crash.
       </para>
 
     </message>

@@ -10020,9 +10022,10 @@
     <message>
 
       <para>
-        An <literal role="stmt" condition="alter-table">ALTER TABLE ...
-        ADD PARTITION</literal> statement run concurrently with a read
-        lock caused spurious
+        An
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE ... ADD PARTITION</literal> statement run concurrently
+        with a read lock caused spurious
         <literal role="error">ER_TABLE_EXISTS_ERROR</literal> and
         <literal role="error">ER_NO_SUCH_TABLE</literal> errors on
         subsequent attempts.

@@ -10053,13 +10056,14 @@
     <message>
 
       <para>
-        <literal role="stmt" condition="alter-table">ALTER TABLE ...
-        TRUNCATE PARTITION</literal>, when called concurrently with
-        transactional DML on the table, was executed immediately and did
-        not wait for the concurrent transaction to release locks. As a
-        result, the <literal role="stmt">ALTER TABLE</literal> statement
-        was written into the binary log before the DML statement, which
-        led to replication failures when using row-based logging.
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE ... TRUNCATE PARTITION</literal>, when called concurrently
+        with transactional DML on the table, was executed immediately
+        and did not wait for the concurrent transaction to release
+        locks. As a result, the <literal role="stmt">ALTER
+        TABLE</literal> statement was written into the binary log before
+        the DML statement, which led to replication failures when using
+        row-based logging.
       </para>
 
     </message>

@@ -14694,12 +14698,13 @@
     <message>
 
       <para>
-        <literal role="stmt">ALTER TABLE</literal> statements that cause
-        table partitions to be renamed or dropped (such as
-        <literal>ALTER TABLE ... ADD PARTITION</literal>, <literal>ALTER
-        TABLE ... DROP PARTITION</literal>, and <literal>ALTER TABLE ...
-        REORGANIZE PARTITION</literal>) &mdash; when run concurrently
-        with queries against the
+        <literal role="stmt" condition="alter-table-partition-operations">ALTER
+        TABLE</literal> statements that cause table partitions to be
+        renamed or dropped (such as <literal>ALTER TABLE ... ADD
+        PARTITION</literal>, <literal>ALTER TABLE ... DROP
+        PARTITION</literal>, and <literal>ALTER TABLE ... REORGANIZE
+        PARTITION</literal>) &mdash; when run concurrently with queries
+        against the
         <literal role="is">INFORMATION_SCHEMA.PARTITIONS</literal> table
         &mdash; could fail, cause the affected partitioned tables to
         become unusable, or both. This was due to the fact that the