List:Commits« Previous MessageNext Message »
From:jon Date:January 21 2006 7:19am
Subject:svn commit - mysqldoc@docsrva: r968 - in trunk: refman-5.1 refman-common
View as plain text  
Author: jstephens
Date: 2006-01-21 08:19:31 +0100 (Sat, 21 Jan 2006)
New Revision: 968

Log:

Added info and warnings relating to Bug #16695 (presence of pre-5.1.6 
partitioned tables on 5.1.6 server makes I_S.PARTITIONS unusable).



Modified:
   trunk/refman-5.1/information-schema.xml
   trunk/refman-5.1/partitioning.xml
   trunk/refman-common/news-5.1.xml

Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml	2006-01-21 06:27:00 UTC (rev 967)
+++ trunk/refman-5.1/information-schema.xml	2006-01-21 07:19:31 UTC (rev 968)
@@ -3643,6 +3643,20 @@
             5.1.6.
           </para>
         </listitem>
+        
+        <listitem>
+          <para>
+            <emphasis role="bold">Important</emphasis>: If any
+            partitioned tables created in a MySQL version prior to MySQL
+            5.1.6 are present following an upgrade to MySQL 5.1.6 or
+            later, it is not possible to <literal>SELECT</literal> from,
+            <literal>SHOW</literal>, or <literal>DESCRIBE</literal> the
+            <literal>PARTITIONS</literal> table. See 
+            <xref linkend="news-5-1-6"/> <emphasis>before</emphasis>
+            upgrading from MySQL 5.1.5 or earlier to MySQL 5.1.6 or
+            later.
+          </para>
+        </listitem>
 
       </itemizedlist>
 

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-01-21 06:27:00 UTC (rev 967)
+++ trunk/refman-5.1/partitioning.xml	2006-01-21 07:19:31 UTC (rev 968)
@@ -39,10 +39,13 @@
   <para>
     <emphasis role="bold">Important</emphasis>: Partitioned tables
     created with MySQL versions prior to 5.1.6 cannot be read by a 5.1.6
-    or later MySQL Server. If you have partitioned tables created in
-    MySQL 5.1.5 or earlier, be sure to see <xref linkend="news-5-1-6"/>
-    for suggested workarounds <emphasis>before</emphasis> upgrading to
-    MySQL 5.1.6 or later.
+    or later MySQL Server. In addition, the
+    <literal>INFORMATION_SCHEMA.TABLES</literal> table cannot be used if
+    such tables are present on a 5.1.6 or later server. If you have
+    partitioned tables which were created in MySQL 5.1.5 or earlier, be
+    sure to see <xref linkend="news-5-1-6"/> for more information and
+    suggested workarounds <emphasis>before</emphasis> upgrading to MySQL
+    5.1.6 or later.
   </para>
 
   <para>

Modified: trunk/refman-common/news-5.1.xml
===================================================================
--- trunk/refman-common/news-5.1.xml	2006-01-21 06:27:00 UTC (rev 967)
+++ trunk/refman-common/news-5.1.xml	2006-01-21 07:19:31 UTC (rev 968)
@@ -82,8 +82,23 @@
           table using <literal>ALTER TABLE ... PARTITION BY
             ...</literal>. Alternatively, you can dump the table using
           <command>mysqldump</command> prior to upgrading and reload it
-          afterwards with <literal>LOAD DATA</literal>. (Bug #13437)
+          afterwards with <literal>LOAD DATA</literal>. In either case,
+          you should drop the pre-5.1.6 partitioned tables before
+          upgrading to 5.1.6 or later. (Bug #13437)       
         </para>
+        
+        <para>
+          <emphasis role="bold">Important</emphasis>: If any partitioned
+          tables that were created prior to MySQL 5.1.6 are present
+          following an upgrade to MySQL 5.1.6 or later, it is also not
+          possible to read from the
+          <literal>INFORMATION_SCHEMA.PARTITIONS</literal> table, nor
+          will you be able to drop those tables or the database or
+          databases in which they are located. In this event, you must:
+          (1) shut down <command>mysqld</command>; (2) manually delete
+          the table, partition, and (if any) subpartition files; and
+          then (3) restart the MySQL Server. (Bug #16695)
+        </para>
       </listitem>
 
       <listitem>

Thread
svn commit - mysqldoc@docsrva: r968 - in trunk: refman-5.1 refman-commonjon21 Jan