svn commit - mysqldoc@docsrva: r5916 - in trunk: refman-4.1 refman-5.0 refman-5.1

[jon]

Author: jstephens
Date: 2007-04-17 13:54:34 +0200 (Tue, 17 Apr 2007)
New Revision: 5916

Log:

Documenting Cluster bugfixes:

  General:      Bug #26176, Bug #27748, Bug #27756, Bug #27758, Bug #27775
  Disk Data:    Bug #27757
  Replication:  Bug #27651, Bug #27728



Modified:
   trunk/refman-4.1/news-4.1.xml
   trunk/refman-5.0/releasenotes-es-5.0.xml
   trunk/refman-5.1/news-5.1.xml


Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml	2007-04-17 11:29:57 UTC (rev 5915)
+++ trunk/refman-4.1/news-4.1.xml	2007-04-17 11:54:34 UTC (rev 5916)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 595 bytes

@@ -687,6 +687,13 @@
           for any subquery without tables. (Bug #24670)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Some queries that updated
+          multiple tables were not backed up correctly. (Bug #27748)
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
===================================================================
--- trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-17 11:29:57 UTC (rev 5915)
+++ trunk/refman-5.0/releasenotes-es-5.0.xml	2007-04-17 11:54:34 UTC (rev 5916)
Changed blocks: 1, Lines Added: 38, Lines Deleted: 0; 1850 bytes

@@ -131,6 +131,44 @@
           privileges. (Bug #27337)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>NDB</literal>
tables
+          having <literal>MEDIUMINT AUTO_INCREMENT</literal> columns
+          were not restored correctly by <command>ndb_restore</command>,
+          causing spurious duplicate key errors. This issue did not
+          affect <literal>TINYINT</literal>,
<literal>INT</literal>, or
+          <literal>BIGINT</literal> columns with
+          <literal>AUTO_INCREMENT</literal>. (Bug #27775)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>NDB</literal>
tables
+          with indexes whose names contained space characters were not
+          restored correctly by <command>ndb_restore</command> (the
+          index names were truncated). (Bug #27758)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Some queries that updated
+          multiple tables were not backed up correctly. (Bug #27748)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Joins on multiple tables
+          containing <literal>BLOB</literal> columns could cause data
+          nodes run out of memory, and to crash with the error
+          <errortext>NdbObjectIdMap::expand unable to
+            expand</errortext>. (Bug #26176) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>


Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml	2007-04-17 11:29:57 UTC (rev 5915)
+++ trunk/refman-5.1/news-5.1.xml	2007-04-17 11:54:34 UTC (rev 5916)
Changed blocks: 1, Lines Added: 78, Lines Deleted: 0; 3174 bytes

@@ -168,6 +168,84 @@
           require the <literal>SELECT</literal> privilege. (Bug #23675)
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Replication): It was possible
+          for API nodes to begin interacting with the cluster
+          subscription manager before they were fully connected to the
+          cluster. (Bug #27651) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Replication): Under very high
+          loads, checkpoints could be read or written with checkpoint
+          indexes out of order. (Bug #27651) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>NDB</literal>
tables
+          having <literal>MEDIUMINT AUTO_INCREMENT</literal> columns
+          were not restored correctly by <command>ndb_restore</command>,
+          causing spurious duplicate key errors. This issue did not
+          affect <literal>TINYINT</literal>,
<literal>INT</literal>, or
+          <literal>BIGINT</literal> columns with
+          <literal>AUTO_INCREMENT</literal>. (Bug #27775)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>NDB</literal>
tables
+          with indexes whose names contained space characters were not
+          restored correctly by <command>ndb_restore</command> (the
+          index names were truncated). (Bug #27758)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Disk Data): Changes to a Disk
+          Data table made as part of a transaction could not be seen by
+          the client performing the changes until the transaction had
+          been committed. (Bug #27757)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: An
<literal>INSERT</literal>
+          followed a delete <literal>DELETE</literal> on the same
+          <literal>NDB</literal> table caused a memory leak. (Bug
+          #27756)
+        </para>
+        
+        <para>
+          (This bug was introduced by the fix for Bug #20612.)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Some queries that updated
+          multiple tables were not backed up or replicated correctly.
+          (Bug #27748) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Joins on multiple tables
+          containing <literal>BLOB</literal> columns could cause data
+          nodes run out of memory, and to crash with the error
+          <errortext>NdbObjectIdMap::expand unable to
+            expand</errortext>. (Bug #26176) 
+        </para>
+      </listitem>
 
       <listitem>
         <para>