MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:March 28 2008 3:13pm
Subject:svn commit - mysqldoc@docsrva: r10363 - in trunk: dynamic-docs/changelog refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2008-03-28 16:13:42 +0100 (Fri, 28 Mar 2008)
New Revision: 10363

Log:

Documenting Partitioning bugfixes:

  Bug #30459, Bug #31931, Bug #32943,
  Bug #33379, Bug #33429, Bug #34358



Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/refman-5.1/partitioning.xml
   trunk/refman-5.1/sql-syntax.xml
   trunk/refman-6.0/partitioning.xml
   trunk/refman-6.0/sql-syntax.xml


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2008-03-28 14:50:15 UTC (rev 10362)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2008-03-28 15:13:42 UTC (rev 10363)
Changed blocks: 1, Lines Added: 156, Lines Deleted: 0; 4011 bytes

@@ -10,6 +10,162 @@
 
     <tags>
       <highlight type="partitioning"/>
+      <manual type="PARTITION BY KEY"/>
+      <manual type="BIT"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="33379"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A table defined using <literal>PARTITION BY KEY</literal> and
+        having a <literal>BIT</literal> column referenced in the
+        partitioning key did not behave correctly; some rows could be
+        inserted into the wrong partition, causing wrong results to be
+        returned from queries.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="partitioning"/>
+      <manual type="DATA DIRECTORY"/>
+      <manual type="INDEX DIRECTORY"/>
+      <manual type="Windows"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="30459"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Using the DATA DIRECTORY and INDEX DIRECTORY options for
+        partitions with CREATE TABLE or ALTER TABLE statements appeared
+        to work on Windows, although they are not supported by MySQL on
+        Windows systems, and subsequent attempts to use the tables
+        referenced caused errors. Now these options are disabled on
+        Windows, and attempting to use them generates a warning.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="partitioning"/>
+      <manual type="ALTER TABLE"/>
+      <manual type="ENGINE"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="31931"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Currently, all partitions of a partitioned table must use the
+        same storage engine. One may optinally specify the storage
+        engine on a per-partition basis; however, where this is the
+        done, the storage engine must be the same as used by the table
+        as a whole. <literal>ALTER TABLE</literal> did not enforce these
+        rules correctly, the result being that incaccurate error
+        messages were shown when trying to use the statement to change
+        the storage engine used by an individual partition or
+        partitions.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="partitioning"/>
+      <manual type="ALTER TABLE DROP PARTITION"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="32943"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        When <literal>ALTER TABLE DROP PARTITION</literal> was executed
+        on a table on which there was a trigger, the statement failed
+        with an error. This occurred even if the trigger did not
+        reference any tables.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="partitioning"/>
+      <manual type="BIT"/>
+    </tags>
+
+    <bugs>
+      <fixes bugid="34358"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.24"/>
+      <version ver="6.0.5"/>
+    </versions>
+
+    <message>
+
+      <para>
+        In some cases, matching rows from a partitioned
+        <literal>MyISAM</literal> using a <literal>BIT</literal> column
+        as the primary key were not found by queries.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <tags>
+      <highlight type="partitioning"/>
       <manual type="InnoDB"/>
       <manual type="innodb_file_per_table"/>
     </tags>


Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2008-03-28 14:50:15 UTC (rev 10362)
+++ trunk/refman-5.1/partitioning.xml	2008-03-28 15:13:42 UTC (rev 10363)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 4; 1966 bytes

@@ -379,7 +379,9 @@
         <para>
           <literal>DATA DIRECTORY</literal> and <literal>INDEX
           DIRECTORY</literal> are not supported for individual
-          partitions or subpartitions on Windows (Bug #30459).
+          partitions or subpartitions on Windows. Beginning with MySQL
+          5.1.24, these options are ignored on Windows, except that a
+          warning is generated. (Bug #30459)
         </para>
       </note>
     </para>

@@ -5230,9 +5232,32 @@
         <title>Same storage engine for all partitions</title>
 
         <para>
-          All of a table's partitions and subpartitions (if there are
-          any of the latter) must use the same storage engine. We are
-          working to remove this limitation in a future MySQL release.
+          All partitions of a partitioned table must use the same
+          storage engine and it must be the same storage engine used by
+          the table as a whole. In addition, if one does not specify an
+          engine on the table level, then one must do either of the
+          following when creating or altering a partitioned table:
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                Do <emphasis>not</emphasis> specify any engine for
+                <emphasis>any</emphasis> partition or subpartition
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Specify the engine for <emphasis>all</emphasis>
+                partitions or subpartitions
+              </para>
+            </listitem>
+
+          </itemizedlist>
+
+          We are working to remove this limitation in a future MySQL
+          release.
         </para>
 
       </formalpara>


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2008-03-28 14:50:15 UTC (rev 10362)
+++ trunk/refman-5.1/sql-syntax.xml	2008-03-28 15:13:42 UTC (rev 10363)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 728 bytes

@@ -4839,7 +4839,9 @@
           <para>
             On Windows, the <literal>DATA DIRECTORY</literal> and
             <literal>INDEX DIRECTORY</literal> options are not supported
-            for individual partitions or subpartitions (Bug #30459).
+            for individual partitions or subpartitions. Beginning with
+            MySQL 5.1.24, these options are ignored on Windows, except
+            that a warning is generated. (Bug #30459)
           </para>
 
           <note>


Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml	2008-03-28 14:50:15 UTC (rev 10362)
+++ trunk/refman-6.0/partitioning.xml	2008-03-28 15:13:42 UTC (rev 10363)
Changed blocks: 2, Lines Added: 29, Lines Deleted: 4; 1969 bytes

@@ -349,7 +349,9 @@
         <para>
           <literal>DATA DIRECTORY</literal> and <literal>INDEX
           DIRECTORY</literal> are not supported for individual
-          partitions or subpartitions on Windows (Bug #30459).
+          partitions or subpartitions on Windows. Beginning with MySQL
+          6.0.5, these options are ignored on Windows, except that a
+          warning is generated. (Bug #30459)
         </para>
       </note>
     </para>

@@ -5133,9 +5135,32 @@
         <title>Same storage engine for all partitions</title>
 
         <para>
-          All of a table's partitions and subpartitions (if there are
-          any of the latter) must use the same storage engine. We are
-          working to remove this limitation in a future MySQL release.
+          All partitions of a partitioned table must use the same
+          storage engine and and it must be the same storage engine used
+          by the table as a whole. In addition, if one does not specify
+          an engine on the table level, then one must do either of the
+          following when creating or altering a partitioned table:
+
+          <itemizedlist>
+
+            <listitem>
+              <para>
+                Do <emphasis>not</emphasis> specify any engine for
+                <emphasis>any</emphasis> partition or subpartition
+              </para>
+            </listitem>
+
+            <listitem>
+              <para>
+                Specify the engine for <emphasis>all</emphasis>
+                partitions or subpartitions
+              </para>
+            </listitem>
+
+          </itemizedlist>
+
+          We are working to remove this limitation in a future MySQL
+          release.
         </para>
 
       </formalpara>


Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml	2008-03-28 14:50:15 UTC (rev 10362)
+++ trunk/refman-6.0/sql-syntax.xml	2008-03-28 15:13:42 UTC (rev 10363)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 1; 730 bytes

@@ -4757,7 +4757,9 @@
           <para>
             On Windows, the <literal>DATA DIRECTORY</literal> and
             <literal>INDEX DIRECTORY</literal> options are not supported
-            for individual partitions or subpartitions (Bug #30459).
+            for individual partitions or subpartitions. Beginning with
+            MySQL 6.0.5, these options are ignored on Windows, except
+            that a warning is generated. (Bug #30459)
           </para>
         </listitem>
 


Thread
svn commit - mysqldoc@docsrva: r10363 - in trunk: dynamic-docs/changelog refman-5.1 refman-6.0jon28 Mar