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

[jon]

Author: jstephens
Date: 2007-05-15 09:02:26 +0200 (Tue, 15 May 2007)
New Revision: 6459

Log:

Reformat.



Modified:
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-05-15 07:00:56 UTC (rev 6458)
+++ trunk/refman-5.1/news-5.1.xml	2007-05-15 07:02:26 UTC (rev 6459)
Changed blocks: 8, Lines Added: 43, Lines Deleted: 41; 4709 bytes

@@ -81,20 +81,21 @@
     </para>
 
     <itemizedlist>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Multiple operations involving
           deletes followed by reads were not handled correctly. (Bug
           #28276)
         </para>
+
         <note>
-        <para>
-          This issue could also affect MySQL Cluster Replication.
-        </para>
+          <para>
+            This issue could also affect MySQL Cluster Replication.
+          </para>
         </note>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (Disk Data): Extremely large

@@ -102,7 +103,7 @@
           in some circumstances. (Bug #27942)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Repeated insertion of data

@@ -111,20 +112,20 @@
           of the cluster. (Bug #27437)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>: Restarting a data node caused
           SQL nodes to log repeatedly and unnecessarily the status of
           the event buffer. (Bug #27292)
         </para>
-        
+
         <para>
           (This issue was known to occur in MySQL 5.1.16 and later
           only.)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>:
<command>ndb_mgmd</command>

@@ -132,7 +133,7 @@
           invalid <literal>[TCP]</literal> entries. (Bug #27207)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal>:

@@ -140,7 +141,7 @@
           output of <literal>SHOW VARIABLES</literal>. (Bug #26675)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           <literal>NDB Cluster</literal> (APIs): In a multi-operation

@@ -149,7 +150,7 @@
           existing value. (Bug #20535)
         </para>
       </listitem>
-      
+
       <listitem>
         <para>
           It was not possible to use the value

@@ -4640,21 +4641,22 @@
       </para>
 
       <itemizedlist>
-      
-      <listitem>
-        <para>
-          Multiple operations involving deletes followed by reads were
-          not handled correctly. (Bug #28276)
-        </para>
-        <note>
-        <para>
-          This issue could also affect MySQL Cluster Replication.
-        </para>
-        </note>
-      </listitem>
 
         <listitem>
           <para>
+            Multiple operations involving deletes followed by reads were
+            not handled correctly. (Bug #28276)
+          </para>
+
+          <note>
+            <para>
+              This issue could also affect MySQL Cluster Replication.
+            </para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para>
             <emphasis role="bold">Cluster APIs</emphasis>: An issue with
             the way in which the
             <literal>NdbDictionary::Dictionary::listEvents()</literal>

@@ -6538,26 +6540,26 @@
       </para>
 
       <itemizedlist>
-      
-      <listitem>
-        <para>
-          <emphasis role="bold">Disk Data</emphasis>: Extremely large
-          inserts into Disk Data tables could lead to data node failure
-          in some circumstances. (Bug #27942)
-        </para>
-      </listitem>
-      
-      <listitem>
-        <para>
-          <emphasis role="bold">Cluster APIs</emphasis>: In a
-          multi-operation transaction, a delete operation followed by
-          the insertion of an implicit <literal>NULL</literal> failed to
-          overwrite an existing value. (Bug #20535)
-        </para>
-      </listitem>
 
         <listitem>
           <para>
+            <emphasis role="bold">Disk Data</emphasis>: Extremely large
+            inserts into Disk Data tables could lead to data node
+            failure in some circumstances. (Bug #27942)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <emphasis role="bold">Cluster APIs</emphasis>: In a
+            multi-operation transaction, a delete operation followed by
+            the insertion of an implicit <literal>NULL</literal> failed
+            to overwrite an existing value. (Bug #20535)
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
             <emphasis role="bold">Cluster Replication</emphasis> /
             <emphasis role="bold">Disk Data</emphasis>: An issue with
             replication of Disk Data tables could in some cases lead to