svn commit - mysqldoc@docsrva: r99 - in trunk: refman-5.0 refman-5.1

[shinz]

Author: shinz
Date: 2005-10-19 17:48:41 +0200 (Wed, 19 Oct 2005)
New Revision: 99

Log:
ARCHIVE supports CHECK TABLE as of 5.0.15

Modified:
   trunk/refman-5.0/storage-engines.xml
   trunk/refman-5.1/storage-engines.xml

Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml	2005-10-19 15:30:20 UTC (rev 98)
+++ trunk/refman-5.0/storage-engines.xml	2005-10-19 15:48:41 UTC (rev 99)
@@ -3723,7 +3723,9 @@
       <ulink url="http://www.zlib.net/">zlib</ulink> lossless data
       compression. Use of <literal>OPTIMIZE TABLE</literal> can analyze
       the table and pack it into a smaller format (for a reason to use
-      <literal>OPTIMIZE TABLE</literal>, see below). There are several
+      <literal>OPTIMIZE TABLE</literal>, see below).
+      Beginning with MySQL 5.0.15, the <literal>ARCHIVE</literal> engine
+      supports <literal>CHECK TABLE</literal>. There are several
       types of insertions that are used:
     </para>
 

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2005-10-19 15:30:20 UTC (rev 98)
+++ trunk/refman-5.1/storage-engines.xml	2005-10-19 15:48:41 UTC (rev 99)
@@ -3721,7 +3721,8 @@
       <ulink url="http://www.zlib.net/">zlib</ulink> lossless data
       compression. Use of <literal>OPTIMIZE TABLE</literal> can analyze
       the table and pack it into a smaller format (for a reason to use
-      <literal>OPTIMIZE TABLE</literal>, see below). There are several
+      <literal>OPTIMIZE TABLE</literal>, see below). The engine supports
+      <literal>CHECK TABLE</literal>, too. There are several
       types of insertions that are used:
     </para>