svn commit - mysqldoc@docsrva: r12937 - in trunk: refman-5.1 refman-6.0

[jon]

Author: jstephens
Date: 2008-12-12 11:16:44 +0100 (Fri, 12 Dec 2008)
New Revision: 12937

Log:

OPRIMIZE used on InnoDB tables now displays 2 lines of output to reflect
more accurately what it is doing (Bug#20129/MattiasJ)



Modified:
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-6.0/sql-syntax-server-administration.xml


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 10:15:30 UTC (rev 12936)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2008-12-12 10:16:44 UTC (rev 12937)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 1; 1654 bytes

@@ -2539,9 +2539,22 @@
         <literal role="stmt">OPTIMIZE TABLE</literal> is mapped to
         <literal role="stmt">ALTER TABLE</literal>, which rebuilds the
         table to update index statistics and free unused space in the
-        clustered index.
+        clustered index. Beginning with MySQL 5.1.27, this is displayed
+        in the output of <literal role="stmt">OPTIMIZE TABLE</literal>
+        when you run it on an <literal>InnoDB</literal> table, as shown
+        here:
       </para>
 
+<programlisting>
+mysql> OPTIMIZE TABLE foo;
++----------+----------+----------+-------------------------------------------------------------------+
+| Table    | Op       | Msg_type | Msg_text                                                          |
++----------+----------+----------+-------------------------------------------------------------------+
+| test.foo | optimize | note     | Table does not support optimize, doing recreate + analyze instead | 
+| test.foo | optimize | status   | OK                                                                | 
++----------+----------+----------+-------------------------------------------------------------------+
+</programlisting>
+
       <para>
         You can make <literal role="stmt">OPTIMIZE TABLE</literal> work
         on other storage engines by starting <command>mysqld</command>


Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 10:15:30 UTC (rev 12936)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml	2008-12-12 10:16:44 UTC (rev 12937)
Changed blocks: 1, Lines Added: 14, Lines Deleted: 1; 1653 bytes

@@ -2431,9 +2431,22 @@
         <literal role="stmt">OPTIMIZE TABLE</literal> is mapped to
         <literal role="stmt">ALTER TABLE</literal>, which rebuilds the
         table to update index statistics and free unused space in the
-        clustered index.
+        clustered index. Beginning with MySQL 6.0.6, this is displayed
+        in the output of <literal role="stmt">OPTIMIZE TABLE</literal>
+        when you run it on an <literal>InnoDB</literal> table, as shown
+        here:
       </para>
 
+<programlisting>
+mysql> OPTIMIZE TABLE foo;
++----------+----------+----------+-------------------------------------------------------------------+
+| Table    | Op       | Msg_type | Msg_text                                                          |
++----------+----------+----------+-------------------------------------------------------------------+
+| test.foo | optimize | note     | Table does not support optimize, doing recreate + analyze instead | 
+| test.foo | optimize | status   | OK                                                                | 
++----------+----------+----------+-------------------------------------------------------------------+
+</programlisting>
+
       <para>
         You can make <literal role="stmt">OPTIMIZE TABLE</literal> work
         on other storage engines by starting <command>mysqld</command>