svn commit - mysqldoc@docsrva: r1348 - trunk/refman-common

[jon]

Author: jstephens
Date: 2006-02-16 15:46:08 +0100 (Thu, 16 Feb 2006)
New Revision: 1348

Log:

Documenting bugfixes:

  Cluster - 17411, 17414, 17415
  Partitioning - 16775, 16782, 16901, 16907



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

Modified: trunk/refman-common/news-5.0.xml
===================================================================
--- trunk/refman-common/news-5.0.xml	2006-02-16 13:21:04 UTC (rev 1347)
+++ trunk/refman-common/news-5.0.xml	2006-02-16 14:46:08 UTC (rev 1348)
@@ -291,6 +291,15 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster log file paths were
+          truncated to 128 characters. They may now be as long as
+          <literal>MAX_PATH</literal> (the maximum path length permitted
+          by the operating system). (Bug #17411)
+        </para>
+      </listitem>
 
       <listitem>
         <para>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-02-16 13:21:04 UTC (rev 1347)
+++ trunk/refman-common/news-5.1.xml	2006-02-16 14:46:08 UTC (rev 1348)
@@ -140,6 +140,66 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          A <literal>SELECT</literal> from the last partition of a
+          subpartitioned table having a <literal>UNIQUE KEY</literal>
+          could crash the MySQL Server. (Bug #16907)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          A <literal>SELECT</literal> on a subpartitioned table having a
+          multiple-column <literal>PRIMARY</literal> or <literal>UNIQUE
+            KEY</literal>, and whose partitioning function used only the
+          first column of the key, could cause <command>mysqld</command>
+          to crash. (Bug #16901)
+        </para> 
+      </listitem>
+      
+      <listitem>
+        <para>
+          Using <literal>REPLACE INTO</literal> on a partitioned table
+          having a primary key would crash the server in the event of a
+          duplicate key error. (Bug #16782)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>DROP TABLE</literal> would sometimes fail on a table
+          having subpartitions that used the default storage engine.
+          (Bug #16775)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Sharing of table names containing
special
+          characters between multiple SQL nodes was not handled
+          correctly when binary logging was enabled (a timeout error
+          resulted). (Bug #17415)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Table definitions were not
+          shared between multiple SQL nodes in a cluster without binary
+          logging being enabled. (Bug #17414)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: Cluster log file paths were
+          truncated to 128 characters. They may now be as long as
+          <literal>MAX_PATH</literal> (the maximum path length permitted
+          by the operating system). (Bug #17411)
+        </para>
+      </listitem>
 
       <listitem>
         <para>