List:Commits« Previous MessageNext Message »
From:jon Date:September 28 2006 5:52am
Subject:svn commit - mysqldoc@docsrva: r3486 - in trunk: refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: jstephens
Date: 2006-09-28 05:52:34 +0200 (Thu, 28 Sep 2006)
New Revision: 3486

Log:

Sorted some misplaced info concerning NDB/SHOW ENGINES - was in main
mysqld section, moved to SHOW ENGINES section and replaced with more
general note/link.

(Thanks, Stefan!)



Modified:
   trunk/refman-4.1/database-administration.xml
   trunk/refman-4.1/sql-syntax.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.0/sql-syntax.xml
   trunk/refman-5.1/database-administration.xml
   trunk/refman-5.1/sql-syntax.xml


Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-4.1/database-administration.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 0; 819 bytes

@@ -331,6 +331,15 @@
 
         </itemizedlist>
 
+        <para>
+          <emphasis role="bold">Note</emphasis>: Not all storage engines
+          (also known in older versions of MySQL as <quote>table
+            types</quote>) are supported by all MySQL server binaries
+          and configurations. To find out how to determine which storage
+          engines are supported by your MySQL server installation, see
+          <xref linkend="show-engines"/>.
+        </para>
+
       </refsection>
 
       <refsection id="server-options">


Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-4.1/sql-syntax.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 611 bytes

@@ -14728,6 +14728,12 @@
           <xref linkend="storage-engines"/>.
         </para>
 
+        <para>
+          All MySQL servers beginning with the 3.23 release series
+          support <literal>MyISAM</literal> tables, because
+          <literal>MyISAM</literal> is the default storage engine.
+        </para>
+
       </section>
 
       <section id="show-errors">


Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-5.0/database-administration.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 744 bytes

@@ -376,6 +376,14 @@
 
         </itemizedlist>
 
+        <para>
+          <emphasis role="bold">Note</emphasis>: Not all storage engines
+          are supported by all MySQL server binaries and configurations.
+          To find out how to determine which storage engines are
+          supported by your MySQL server installation, see 
+          <xref linkend="show-engines"/>.
+        </para>
+
       </refsection>
 
       <refsection id="mysqld-option-tables">


Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-5.0/sql-syntax.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 8; 3569 bytes

@@ -16494,18 +16494,74 @@
 Support: YES
 Comment: /dev/null storage engine (anything you write to it disappears)
 </programlisting>
+        
+        <para>
+          The output from <literal>SHOW ENGINES</literal> may vary
+          according to the MySQL version used and other factors. The
+          values shown in the <literal>Support</literal> column indicate
+          the server's level of support for different features, as shown
+          here:
+        </para>
 
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="15*"/>
+            <colspec colwidth="85*"/>
+            <tbody>
+              <row>
+                <entry><emphasis
role="bold">Value</emphasis></entry>
+                <entry><emphasis
role="bold">Meaning</emphasis></entry>
+              </row>
+              <row>
+                <entry><literal>YES</literal></entry>
+                <entry>The feature is supported and is active.</entry>
+              </row>
+              <row>
+                <entry><literal>NO</literal></entry>
+                <entry>The feature is not supported.</entry>
+              </row>
+              <row>
+                <entry><literal>DISABLED</literal></entry>
+                <entry>The feature is supported but has been
disabled.</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
+
         <para>
-          The <literal>Support</literal> value indicates whether the
-          particular storage engine is supported, and which is the
-          default engine. For example, if the server is started with the
-          <option>--default-table-type=InnoDB</option> option, the
-          <literal>Support</literal> value for the
-          <literal>InnoDB</literal> row has the value
-          <literal>DEFAULT</literal>. See
-          <xref linkend="storage-engines"/>.
+          A value of <literal>NO</literal> means that the server was
+          compiled without support for the feature, so it cannot be
+          activated at runtime.
         </para>
 
+        <para>
+          A value of <literal>DISABLED</literal> occurs either because
+          the server was started with an option that disables the
+          feature, or because not all options required to enable it were
+          given. In the latter case, the error log file should contain a
+          reason indicating why the option is disabled. See
+          <xref linkend="error-log"/>.
+        </para>
+
+        <para>
+          You might also see <literal>DISABLED</literal> for a storage
+          engine if the server was compiled to support it, but was
+          started with a
+         
<option>--skip-<replaceable>engine</replaceable></option>
+          option. For example, <option>--skip-innodb</option> disables
+          the <literal>InnoDB</literal> engine. For the <literal>NDB
+          Cluster</literal> storage engine, <literal>DISABLED</literal>
+          means the server was compiled with support for MySQL Cluster,
+          but was not started with the <option>--ndb-cluster</option>
+          option.
+        </para>
+
+        <para>
+          All MySQL servers support <literal>MyISAM</literal> tables,
+          because <literal>MyISAM</literal> is the default storage
+          engine.
+        </para>
+
       </section>
 
       <section id="show-errors">


Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-5.1/database-administration.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 182; 7206 bytes

@@ -360,190 +360,13 @@
         </itemizedlist>
 
         <para>
-          Currently, MySQL Cluster is supported on Linux (on most
-          platforms), Solaris, Mac OS X, and HP-UX only. Some users have
-          reported success in using MySQL Cluster built from source on
-          BSD operating systems, but these are not officially supported
-          at this time. Note that, even for servers compiled with
-          Cluster support, the <literal>NDB Cluster</literal> storage
-          engine is not enabled by default. You must start the server
-          with the <option>--ndbcluster</option> option to use it as
-          part of a MySQL Cluster. (For details, see
-          <xref linkend="mysql-cluster-configuration"/>.)
+          <emphasis role="bold">Note</emphasis>: Not all storage engines
+          are supported by all MySQL server binaries and configurations.
+          To find out how to determine which storage engines are
+          supported by your MySQL server installation, see 
+          <xref linkend="show-engines"/>.
         </para>
 
-        <para>
-          The following table shows the platforms for which MySQL server
-          binaries include support for <literal>NDB Cluster</literal>.
-        </para>
-
-        <informaltable>
-          <tgroup cols="2">
-            <colspec colwidth="50*"/>
-            <colspec colwidth="25*"/>
-            <tbody>
-              <row>
-                <entry><emphasis
role="bold">System</emphasis></entry>
-                <entry><emphasis role="bold">NDB
Support</emphasis></entry>
-              </row>
-              <row>
-                <entry>AIX 5.2</entry>
-                <entry>N</entry>
-              </row>
-              <row>
-                <entry>HP-UX</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Linux-IA-64</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Linux-Intel</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Mac OS X</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>NetWare</entry>
-                <entry>N</entry>
-              </row>
-              <row>
-                <entry>SCO 6</entry>
-                <entry>N</entry>
-              </row>
-              <row>
-                <entry>Solaris-SPARC</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Solaris-Intel</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Solaris-AMD 64</entry>
-                <entry>Y</entry>
-              </row>
-              <row>
-                <entry>Windows NT/2000/XP</entry>
-                <entry>N</entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable>
-
-        <remark>
-          Output for SHOW statement following is from 5.1.6-alpha-log
-        </remark>
-
-        <para>
-          To find out which storage engines your server supports, use
-          the <literal>SHOW ENGINES</literal> statement. (See
-          <xref linkend="show-engines"/>.) For example:
-        </para>
-
-<programlisting>
-mysql&gt; <userinput>SHOW ENGINES\G</userinput>
-*************************** 1. row ***************************
-      Engine: MEMORY
-     Support: YES
-     Comment: Hash based, stored in memory, useful for temporary tables
-Transactions: NO
-          XA: NO
-  Savepoints: NO
-*************************** 2. row ***************************
-      Engine: CSV
-     Support: YES
-     Comment: CSV storage engine
-Transactions: NO
-          XA: NO
-  Savepoints: NO
-*************************** 3. row ***************************
-      Engine: MRG_MYISAM
-     Support: YES
-     Comment: Collection of identical MyISAM tables
-Transactions: NO
-          XA: NO
-  Savepoints: NO
-*************************** 4. row ***************************
-      Engine: MyISAM
-     Support: DEFAULT
-     Comment: Default engine as of MySQL 3.23 with great performance
-Transactions: NO
-          XA: NO
-  Savepoints: NO
-...
-</programlisting>
-
-        <para>
-          The precise output from <literal>SHOW ENGINES</literal> may
-          vary according to the MySQL version used (and the features
-          that are enabled). The <literal>Support</literal> values in
-          the output indicate the server's level of support for each
-          feature, as shown here:
-        </para>
-
-        <informaltable>
-          <tgroup cols="2">
-            <colspec colwidth="15*"/>
-            <colspec colwidth="85*"/>
-            <tbody>
-              <row>
-                <entry><emphasis
role="bold">Value</emphasis></entry>
-                <entry><emphasis
role="bold">Meaning</emphasis></entry>
-              </row>
-              <row>
-                <entry><literal>YES</literal></entry>
-                <entry>The feature is supported and is active.</entry>
-              </row>
-              <row>
-                <entry><literal>NO</literal></entry>
-                <entry>The feature is not supported.</entry>
-              </row>
-              <row>
-                <entry><literal>DISABLED</literal></entry>
-                <entry>The feature is supported but has been
disabled.</entry>
-              </row>
-            </tbody>
-          </tgroup>
-        </informaltable>
-
-        <para>
-          A value of <literal>NO</literal> means that the server was
-          compiled without support for the feature, so it cannot be
-          activated at runtime.
-        </para>
-
-        <para>
-          A value of <literal>DISABLED</literal> occurs either because
-          the server was started with an option that disables the
-          feature, or because not all options required to enable it were
-          given. In the latter case, the error log file should contain a
-          reason indicating why the option is disabled. See
-          <xref linkend="error-log"/>.
-        </para>
-
-        <para>
-          You might also see <literal>DISABLED</literal> for a storage
-          engine if the server was compiled to support it, but was
-          started with a
-         
<option>--skip-<replaceable>engine</replaceable></option>
-          option. For example, <option>--skip-innodb</option> disables
-          the <literal>InnoDB</literal> engine. For the <literal>NDB
-          Cluster</literal> storage engine, <literal>DISABLED</literal>
-          means the server was compiled with support for MySQL Cluster,
-          but was not started with the <option>--ndb-cluster</option>
-          option.
-        </para>
-
-        <para>
-          All MySQL servers support <literal>MyISAM</literal> tables,
-          because <literal>MyISAM</literal> is the default storage
-          engine.
-        </para>
-
       </refsection>
 
       <refsection id="mysqld-option-tables">


Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml	2006-09-27 22:30:29 UTC (rev 3485)
+++ trunk/refman-5.1/sql-syntax.xml	2006-09-28 03:52:34 UTC (rev 3486)
Changed blocks: 1, Lines Added: 64, Lines Deleted: 8; 3691 bytes

@@ -17974,19 +17974,75 @@
           XA: NO
   Savepoints: NO
 </programlisting>
+        
+        <para>
+          The output from <literal>SHOW ENGINES</literal> may vary
+          according to the MySQL version used and other factors. The
+          values shown in the <literal>Support</literal> column indicate
+          the server's level of support for different features, as shown
+          here:
+        </para>
 
+        <informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="15*"/>
+            <colspec colwidth="85*"/>
+            <tbody>
+              <row>
+                <entry><emphasis
role="bold">Value</emphasis></entry>
+                <entry><emphasis
role="bold">Meaning</emphasis></entry>
+              </row>
+              <row>
+                <entry><literal>YES</literal></entry>
+                <entry>The feature is supported and is active.</entry>
+              </row>
+              <row>
+                <entry><literal>NO</literal></entry>
+                <entry>The feature is not supported.</entry>
+              </row>
+              <row>
+                <entry><literal>DISABLED</literal></entry>
+                <entry>The feature is supported but has been
disabled.</entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable>
+
         <para>
-          The <literal>Support</literal> value indicates whether the
-          particular storage engine is supported, and which is the
-          default engine. For example, if the server is started with the
-          <option>--default-table-type=InnoDB</option> option, the
-          <literal>Support</literal> value for the
-          <literal>InnoDB</literal> row has the value
-          <literal>DEFAULT</literal>. See
-          <xref linkend="storage-engines"/>.
+          A value of <literal>NO</literal> means that the server was
+          compiled without support for the feature, so it cannot be
+          activated at runtime.
         </para>
 
         <para>
+          A value of <literal>DISABLED</literal> occurs either because
+          the server was started with an option that disables the
+          feature, or because not all options required to enable it were
+          given. In the latter case, the error log file should contain a
+          reason indicating why the option is disabled. See
+          <xref linkend="error-log"/>.
+        </para>
+
+        <para>
+          You might also see <literal>DISABLED</literal> for a storage
+          engine if the server was compiled to support it, but was
+          started with a
+         
<option>--skip-<replaceable>engine</replaceable></option>
+          option. For example, <option>--skip-innodb</option> disables
+          the <literal>InnoDB</literal> engine. For the <literal>NDB
+          Cluster</literal> storage engine, <literal>DISABLED</literal>
+          means the server was compiled with support for MySQL Cluster,
+          but was not started with the <option>--ndb-cluster</option>
+          option.
+        </para>
+
+        <para>
+          All MySQL servers support <literal>MyISAM</literal> tables,
+          because <literal>MyISAM</literal> is the default storage
+          engine.
+        </para>
+
+        <para>
           The <literal>Transactions</literal>,
<literal>XA</literal>,
           and <literal>Savepoints</literal> columns were added in MySQL
           5.1.2. They indicate whether the storage engine supports


Thread
svn commit - mysqldoc@docsrva: r3486 - in trunk: refman-4.1 refman-5.0 refman-5.1jon28 Sep