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

[jon]

Author: jstephens
Date: 2006-01-24 13:02:23 +0100 (Tue, 24 Jan 2006)
New Revision: 1016

Log:

Documenting bugfixes:

  Partitioning: 15523, 15966, 16534, 16718
  Cluster: 13556, 16742
  
  Updated 5.1 Partitioning chapter to reflect bugfixes and feature changes.



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	2006-01-24 08:18:21 UTC (rev 1015)
+++ trunk/refman-5.1/partitioning.xml	2006-01-24 12:02:23 UTC (rev 1016)
@@ -250,11 +250,13 @@
       variable with the value <literal>YES</literal> listed as shown
       above in the output of an appropriate <literal>SHOW
       VARIABLES</literal>, then your version of MySQL does not support
-      partitioning. (Note that there is nothing in the output of
-      <literal>SHOW ENGINES</literal> that displays any information
-      relating to partitioning support; you must use <literal>SHOW
-      VARIABLES</literal> to make this determination.)
+      partitioning.
     </para>
+    
+    <para>
+      Prior to MySQL 5.1.6, this variable was named
+      <literal>have_partition_engine</literal>. (Bug #16718)      
+    </para>
 
     <para>
       For creating partitioned tables, you can use any storage engine
@@ -2064,12 +2066,10 @@
     </para>
 
     <para>
-      <emphasis role="bold">Important</emphasis>: Currently,
-      <literal>ALTER TABLE ... PARTITION BY ...</literal> is accepted as
-      valid syntax by a MySQL server built from the 5.1 tree, but the
-      statement actually does nothing. We expect to implement the
-      behavior of this statement as described below by the time that
-      MySQL 5.1 reaches production status.
+      The statement <literal>ALTER TABLE ... PARTITION BY ...</literal>
+      is available and is functional beginning with MySQL 5.1.6;
+      previously in MySQL 5.1, this was accepted as valid syntax, but the
+      statement did nothing. 
     </para>
 
     <para>
@@ -2429,7 +2429,33 @@
         dealing with a large amounts of data. This also might not be
         feasible in situations where high availability is a requirement.
       </para>
+      
+      <para>
+        Beginning with MySQL 5.1.6, you can add multiple partitions in a
+        single <literal>ALTER TABLE ... ADD PARTITION</literal>
+        statement as shown here:
+      </para>
+      
+<programlisting>
+CREATE TABLE employees (
+  id INT NOT NULL,
+  fname VARCHAR(50) NOT NULL,
+  lname VARCHAR(50) NOT NULL,
+  hired DATE NOT NULL
+)
+PARTITION BY RANGE( YEAR(hired) ) (
+  PARTITION p1 VALUES LESS THAN (1991),
+  PARTITION p2 VALUES LESS THAN (1996),
+  PARTITION p3 VALUES LESS THAN (2001),
+  PARTITION p4 VALUES LESS THAN (2005)
+);
 
+ALTER TABLE employees ADD PARTITION (
+    PARTITION p5 VALUES LESS THAN (2010), 
+    PARTITION p6 VALUES LESS THAN MAXVALUE
+);
+</programlisting>
+
       <para>
         Fortunately, MySQL's partitioning implementation provides ways
         to redefine partitions without losing data. Let us look first at

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-24 08:18:21 UTC (rev 1015)
+++ trunk/refman-common/news-5.1.xml	2006-01-24 12:02:23 UTC (rev 1016)
@@ -118,7 +118,7 @@
         <para>
           Partition support is not an <quote>engine</quote>, but it was
           included in the output of <literal>SHOW ENGINES</literal>. Now
-          it does not. (Bug #14355) The
+          it is not. (Bug #14355) The
           <literal>have_partition_engine</literal> was renamed to
           <literal>have_partitioning</literal>. (Bug #16718)
         </para>
@@ -174,6 +174,50 @@
     </para>
 
     <itemizedlist>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal> (Disk Data): Tablespaces
+          created using parameters with relatively low values (&lt; 10
+          MB) produced filesizes much smaller than expected. (Bug
+          #16742)          
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>NDB Cluster</literal>: <literal>CREATE
+            TABLESPACE</literal> statements were incorrectly parsed on
+          64-bit platforms. (<literal>INITIAL SIZE
+            <replaceable>size</replaceable></literal> worked, but
+          <literal>INITIAL SIZE =
+          <replaceable>size</replaceable></literal> failed.) (Bug
+          #13556)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Trying to add more than one partition in a single
+          <literal>ALTER TABLE ... ADD PARTITION</literal> statement
+          caused the server to crash. (Bug #16534)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          Creating a partitioned table using a storage engine other than
+          the session default storage engine caused the server to crash.
+          (Bug #15966)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          An <literal>ALTER TABLE ... PARTITION BY ...</literal>
+          statement did not have any effect. (Bug #15523)
+        </para>
+      </listitem>
 
       <listitem>
         <para>