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

[jon]

Author: jstephens
Date: 2006-06-14 03:31:36 +0200 (Wed, 14 Jun 2006)
New Revision: 2370

Log:
Documenting Partitioning bugfixes:
  Bug #19122/Bug #19903/Bug #19803, Bug #19305, Bug #19307, Bug #19695

CSV tables do not support partitioning

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

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-06-14 00:50:50 UTC (rev 2369)
+++ trunk/refman-5.1/partitioning.xml	2006-06-14 01:31:36 UTC (rev 2370)
@@ -266,13 +266,14 @@
 
     <para>
       <emphasis role="bold">Note</emphasis>: MySQL partitioning cannot
-      be used with the <literal>MERGE</literal> storage engine. Prior to
-      MySQL 5.1.6, it was also not feasible to create a partitioned
-      table using the <literal>BLACKHOLE</literal> storage engine. (Bug
-      #14524). Partitioning by <literal>KEY</literal> is supported for
-      use with the <literal>NDBCluster</literal> storage engine, but
-      other types of user-defined partitioning are not supported for
-      Cluster tables in MySQL &current-series;.
+      be used with the <literal>MERGE</literal> or
+      <literal>CSV</literal> storage engines. Prior to MySQL 5.1.6, it
+      was also not feasible to create a partitioned table using the
+      <literal>BLACKHOLE</literal> storage engine. (Bug #14524).
+      Partitioning by <literal>KEY</literal> is supported for use with
+      the <literal>NDBCluster</literal> storage engine, but other types
+      of user-defined partitioning are not supported for Cluster tables
+      in MySQL &current-series;.
     </para>
 
     <para>
@@ -3947,23 +3948,30 @@
       </listitem>
 
       <listitem>
-        
+
         <indexterm>
           <primary>partitioning</primary>
           <secondary>storage engines (limitations)</secondary>
         </indexterm>
-        
+
         <para>
           Tables using the <literal>MERGE</literal> storage engine
           cannot be partitioned.
         </para>
 
         <para>
+          Partitioned tables using the <literal>CSV</literal> storage
+          engine are not supported. Starting with MySQL 5.1.12, it is
+          not possible to create partitioned <literal>CSV</literal>
+          tables at all.
+        </para>
+
+        <para>
           Prior to MySQL 5.1.6, tables using the
           <literal>BLACKHOLE</literal> storage engine also could not be
           partitioned.
         </para>
-        
+
         <para>
           Partitioning by <literal>KEY</literal> is the only type of
           partitioning supported for the <literal>NDBCluster</literal>

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-06-14 00:50:50 UTC (rev 2369)
+++ trunk/refman-5.1/storage-engines.xml	2006-06-14 01:31:36 UTC (rev 2370)
@@ -3985,6 +3985,13 @@
       <emphasis role="bold">Important</emphasis>: The
       <literal>CSV</literal> storage engine does not support indexing.
     </para>
+    
+    <para>
+      Partitioning is not supported for tables using the
+      <literal>CSV</literal> storage engine. Beginning with MySQL
+      5.1.12, it is no longer possible to create partitioned
+      <literal>CSV</literal> tables. (See Bug #19307)
+    </para>
 
   </section>
 

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-06-14 00:50:50 UTC (rev 2369)
+++ trunk/refman-common/news-5.1.xml	2006-06-14 01:31:36 UTC (rev 2370)
@@ -143,6 +143,13 @@
           Added the <literal>SHOW CONTRIBUTORS</literal> statement.
         </para>
       </listitem>
+      
+      <listitem>
+        <para>
+          It is no longer possible to create partitioned tables using
+          the <literal>CSV</literal> storage engine.
+        </para>
+      </listitem>
 
     </itemizedlist>
 
@@ -154,6 +161,30 @@
       
       <listitem>
         <para>
+          The <literal>EGNINE</literal> clause was displayed in the
+          output of <literal>SHOW CREATE TABLE</literal> for partitioned
+          tables when the SQL mode included
+          <literal>no_table_options</literal>. (Bug #19695) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ALTER TABLE ... COALESCE PARTITION</literal> did not
+          delete the files associated with the partitions that were
+          removed. (Bug #19305) 
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
+          <literal>ALTER TABLE ... REBUILD PARTITION</literal> could
+          cause the server to hang or crash. (Bug #19122)
+        </para>
+      </listitem>
+      
+      <listitem>
+        <para>
           <literal>NDB Cluster</literal> (Disk Data): Running a large
           nbumber of scans on Disk Data could cause subsequent scans to
           perform poorly. (Bug #20334)