svn commit - mysqldoc@docsrva: r600 - in trunk: refman-5.1 refman-common

[jon]

Author: jstephens
Date: 2005-12-20 15:04:39 +0100 (Tue, 20 Dec 2005)
New Revision: 600

Log:

Documenting Partitioning bugfixes: Bug#15521, Bug#15524 (Thanks, Kolbe!)



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

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2005-12-20 13:17:14 UTC (rev 599)
+++ trunk/refman-5.1/partitioning.xml	2005-12-20 14:04:39 UTC (rev 600)
@@ -2559,6 +2559,14 @@
             or sets of values (when reorganizing tables partitioned by
             <literal>LIST</literal>).
           </para>
+          
+          <para>
+            <emphasis role="bold">Note</emphasis>: Prior to MySQL 5.1.4,
+            you could not reuse the names of existing partitions in the
+            <literal>INTO</literal> clause, even when those partitions
+            were being dropped or redefined. See 
+            <xref linkend="news-5-1-4"/> for more information.
+          </para>
         </listitem>
 
         <listitem>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2005-12-20 13:17:14 UTC (rev 599)
+++ trunk/refman-common/news-5.1.xml	2005-12-20 14:04:39 UTC (rev 600)
@@ -89,9 +89,56 @@
     </para>
 
     <itemizedlist>
+      <listitem>
+        <para>
+          The server produced a non-descriptive error message when
+          attempting to insert an out-of-range value into a partitioned
+          table. The server now returns the error <errortext>Table has
+            no partition for value
+            <replaceable>val</replaceable></errortext>, where
+          <replaceable>val</replaceable> is the out-of-range value. 
+          (Bug #15524)
+        </para>
+      </listitem>
       
       <listitem>
         <para>
+          It was not possible to reorganize a partition reusing a
+          discarded partition name.
+        </para>
+        
+        <para>
+          Now, for example, you can create a table such as this one: 
+        </para>
+
+<programlisting>
+CREATE TABLE t1 (a INT) 
+    PARTITION BY RANGE (a) (
+      PARTITION p0 VALUES LESS THAN (10),
+      PARTITION p1 VALUES LESS THAN (20),
+      PARTITION p2 VALUES LESS THAN MAXVALUE
+    );
+</programlisting>
+        
+        <para>
+          and then repartition it as shown here:
+        </para>
+        
+<programlisting>
+ALTER TABLE t1 REORGANIZE PARTITION p2 INTO (
+    PARTITION p2 VALUES LESS THAN (30)
+);
+</programlisting>
+        
+        <para>
+          Previously, attempting to do so would produce the error
+          <errortext>All partitions must have unique names in the
+            table</errortext>. (Bug #15521)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal>: The <option>--ndb</option>
           option for <command>perror</command> did not function.
           (Bug #15486)