svn commit - mysqldoc@docsrva: r6711 - trunk/refman-5.1

[jon]

Author: jstephens
Date: 2007-06-08 10:56:20 +0200 (Fri, 08 Jun 2007)
New Revision: 6711

Log:

Added warning about partitioned tables to downgrading-to-5.0 (Thanks, Omer!)



Modified:
   trunk/refman-5.1/installing.xml


Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2007-06-08 05:47:18 UTC (rev 6710)
+++ trunk/refman-5.1/installing.xml	2007-06-08 08:56:20 UTC (rev 6711)
Changed blocks: 1, Lines Added: 53, Lines Deleted: 6; 2770 bytes

@@ -13063,15 +13063,62 @@
     <section id="downgrading-to-5-0">
 
       <title>Downgrading to MySQL 5.0</title>
-
+      
       <para>
-        MySQL 5.0 does not support events. If your databases contain
-        events, prevent them from being dumped when you use
-        <command>mysqldump</command> by using the
-        <option>--skip-events</option> option. (See
-        <xref linkend="mysqldump"/>.)
+        When downgrading to MySQL 5.0 from MySQL 5.1 or a later version,
+        you should keep in mind the following issues relating to
+        features found in MySQL 5.1 and later, but not in MySQL 5.0:  
       </para>
+      
+      <itemizedlist>
+        <listitem>
+          <formalpara>
+            <title>Event Scheduler</title>
+            
+            <para>
+              MySQL 5.0 does not support scheduled events. If your
+              databases contain scheduled event definitions, you should
+              prevent them from being dumped when you use
+              <command>mysqldump</command> by using the
+              <option>--skip-events</option> option. (See 
+              <xref linkend="mysqldump"/>.)
+            </para>
+          </formalpara>          
+        </listitem>
+        
+        <listitem>
+          <formalpara>
+            <title>Partitioning</title>
+            
+            <para>
+              MySQL 5.0 does not support user-defined partitioning. If a
+              table was created as a partitioned table in 5.1 (or if an
+              table created in a previous version of MySQL was altered
+              to include partitions after an upgrade to 5.1), the table
+              is accessible after downgrade only if you do one of the
+              following: 
+              
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    Export the table using <command>mysqldump</command>
+                    and then drop it in MySQL 5.1; import the table
+                    again following the downgrade to MySQL 5.0.
+                  </para>
+                </listitem>
 
+                <listitem>
+                  <para>
+                    Prior to the downgrade, remove the table's
+                    partitioning using <literal>ALTER TABLE
+                      <replaceable>table_name</replaceable> REMOVE
+                      PARTITIONING</literal>.
+                  </para>
+            </listitem>
+          </itemizedlist>
+        </para>
+      </formalpara>
+      </listitem></itemizedlist>
     </section>
 
   </section>