List:Commits« Previous MessageNext Message »
From:jon Date:November 13 2007 1:32pm
Subject:svn commit - mysqldoc@docsrva: r8679 - in trunk: refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2007-11-13 14:32:05 +0100 (Tue, 13 Nov 2007)
New Revision: 8679

Log:

DATA DIRECTORY and INDEX DIRECTORY partitioning options don't work for 
InnoDB tables (Thanks, DavidS!)

Plus a couple of other minor fixups



Modified:
   trunk/refman-5.1/partitioning.xml
   trunk/refman-6.0/partitioning.xml


Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2007-11-13 12:12:56 UTC (rev 8678)
+++ trunk/refman-5.1/partitioning.xml	2007-11-13 13:32:05 UTC (rev 8679)
Changed blocks: 5, Lines Added: 24, Lines Deleted: 13; 2482 bytes

@@ -283,10 +283,12 @@
       partitioning.
     </para>
 
-    <para>
-      Prior to MySQL 5.1.6, this variable was named
-      <literal>have_partition_engine</literal>. (Bug #16718)
-    </para>
+    <note>
+      <para>
+        Prior to MySQL 5.1.6, this variable was named
+        <literal>have_partition_engine</literal>. (Bug #16718)
+      </para>
+    </note>
 
     <para>
       For creating partitioned tables, you can use most storage engines

@@ -336,11 +338,13 @@
     PARTITIONS 6;
 </programlisting>
 
-    <para>
-      (Note that each <literal>PARTITION</literal> clause can include a
-      <literal>[STORAGE] ENGINE</literal> option, but in MySQL
-      &current-series; this has no effect.)
-    </para>
+    <note>
+      <para>
+        Each <literal>PARTITION</literal> clause can include a
+        <literal>[STORAGE] ENGINE</literal> option, but in MySQL
+        &current-series; this has no effect.
+      </para>
+    </note>
 
     <important>
       <para>

@@ -354,9 +358,9 @@
     <para>
       Data and indexes for each partition can be assigned to a specific
       directory using the <literal>DATA DIRECTORY</literal> and
-      <literal>INDEX DIRECTORY</literal> options for the PARTITION
-      clause of the <literal>CREATE TABLE</literal> statement used to
-      create the partitioned table.
+      <literal>INDEX DIRECTORY</literal> options for the
+      <literal>PARTITION</literal> clause of the <literal>CREATE
+      TABLE</literal> statement used to create the partitioned table.
 
       <note>
         <para>

@@ -364,6 +368,13 @@
           the <literal>NO_DIR_IN_CREATE</literal> server SQL mode was in
           effect. (Bug #24633)
         </para>
+
+        <para>
+          The <literal>DATA DIRECTORY</literal> and <literal>INDEX
+          DIRECTORY</literal> options have no effect when defining
+          partitions for tables using the <literal>InnoDB</literal>
+          storage engine.
+        </para>
       </note>
     </para>
 

@@ -378,7 +389,7 @@
 CREATE TABLE sales1 (
     id INT(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
     sales_date DATE NOT NULL DEFAULT '0000-00-00'
-) ENGINE=InnoDB DEFAULT CHARSET=latin1
+) ENGINE=MyISAM DEFAULT CHARSET=latin1
 PARTITION BY RANGE(id)
 (
     PARTITION p0 VALUES LESS THAN (5000)


Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml	2007-11-13 12:12:56 UTC (rev 8678)
+++ trunk/refman-6.0/partitioning.xml	2007-11-13 13:32:05 UTC (rev 8679)
Changed blocks: 3, Lines Added: 20, Lines Deleted: 9; 1902 bytes

@@ -308,11 +308,13 @@
     PARTITIONS 6;
 </programlisting>
 
-    <para>
-      (Note that each <literal>PARTITION</literal> clause can include a
-      <literal>[STORAGE] ENGINE</literal> option, but in MySQL
-      &current-series; this has no effect.)
-    </para>
+    <note>
+      <para>
+        Each <literal>PARTITION</literal> clause can include a
+        <literal>[STORAGE] ENGINE</literal> option, but in MySQL
+        &current-series; this has no effect.
+      </para>
+    </note>
 
     <important>
       <para>

@@ -326,9 +328,18 @@
     <para>
       Data and indexes for each partition can be assigned to a specific
       directory using the <literal>DATA DIRECTORY</literal> and
-      <literal>INDEX DIRECTORY</literal> options for the PARTITION
-      clause of the <literal>CREATE TABLE</literal> statement used to
-      create the partitioned table.
+      <literal>INDEX DIRECTORY</literal> options for the
+      <literal>PARTITION</literal> clause of the <literal>CREATE
+      TABLE</literal> statement used to create the partitioned table.
+
+      <note>
+        <para>
+          The <literal>DATA DIRECTORY</literal> and <literal>INDEX
+          DIRECTORY</literal> options have no effect when defining
+          partitions for tables using the <literal>InnoDB</literal>
+          storage engine.
+        </para>
+      </note>
     </para>
 
     <important>

@@ -342,7 +353,7 @@
 CREATE TABLE sales1 (
     id INT(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
     sales_date DATE NOT NULL DEFAULT '0000-00-00'
-) ENGINE=InnoDB DEFAULT CHARSET=latin1
+) ENGINE=MyISAM DEFAULT CHARSET=latin1
 PARTITION BY RANGE(id)
 (
     PARTITION p0 VALUES LESS THAN (5000)


Thread
svn commit - mysqldoc@docsrva: r8679 - in trunk: refman-5.1 refman-6.0jon13 Nov