Author: paul
Date: 2006-01-13 03:42:39 +0100 (Fri, 13 Jan 2006)
New Revision: 793
Log:
r6144@frost: paul | 2006-01-12 20:36:55 -0600
More uniform introduction to storage engine sections.
Modified:
trunk/
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/storage-engines.xml
trunk/refman-5.1/storage-engines.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6143
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6144
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2006-01-13 02:42:20 UTC (rev 792)
+++ trunk/refman-4.1/storage-engines.xml 2006-01-13 02:42:39 UTC (rev 793)
@@ -2638,7 +2638,7 @@
<para>
If you build MySQL from source, you can enable
- <literal>BDB</literal> support by running
+ <literal>BDB</literal> support by invoking
<command>configure</command> with the
<option>--with-berkeley-db</option> option in addition to any
other options that you normally use. Download a distribution for
@@ -3286,15 +3286,16 @@
</para>
<para>
- To examine the source for the <literal>EXAMPLE</literal> engine,
- look in the <filename>sql/examples</filename> directory of a
- source distribution for MySQL 4.1.3 or newer.
+ The <literal>EXAMPLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-example-storage-engine</option> option.
</para>
<para>
- To enable this storage engine, use the
- <option>--with-example-storage-engine</option> option to
- <command>configure</command> when you build MySQL.
+ To examine the source for the <literal>EXAMPLE</literal> engine,
+ look in the <filename>sql/examples</filename> directory of a MySQL
+ source distribution.
</para>
<para>
@@ -3352,12 +3353,23 @@
</para>
<para>
- To enable this storage engine, use the
- <option>--with-archive-storage-engine</option> option to
- <command>configure</command> when you build MySQL. You can see if
- this storage engine is available with this statement:
+ The <literal>ARCHIVE</literal> storage engine is included in MySQL
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-archive-storage-engine</option> option.
</para>
+ <para>
+ To examine the source for the <literal>ARCHIVE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
+ You can check whether the <literal>ARCHIVE</literal> storage
+ engine is available with this statement:
+ </para>
+
<programlisting>
mysql> <userinput>SHOW VARIABLES LIKE 'have_archive';</userinput>
</programlisting>
@@ -3475,6 +3487,19 @@
</para>
<para>
+ The <literal>CSV</literal> storage engine is included in MySQL-Max
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-csv-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>CSV</literal> engine, look
+ in the <filename>sql/examples</filename> directory of a MySQL
+ source distribution.
+ </para>
+
+ <para>
When you create a <literal>CSV</literal> table, the server creates
a table definition file in the database directory. The file begins
with the table name and has an <filename>.frm</filename>
@@ -3558,6 +3583,19 @@
</programlisting>
<para>
+ The <literal>BLACKHOLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-blackhole-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>BLACKHOLE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
When you create a <literal>BLACKHOLE</literal> table, the server
creates a table definition file in the database directory. The
file begins with the table name and has an
Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml 2006-01-13 02:42:20 UTC (rev 792)
+++ trunk/refman-5.0/storage-engines.xml 2006-01-13 02:42:39 UTC (rev 793)
@@ -2619,7 +2619,7 @@
<para>
If you build MySQL from source, you can enable
- <literal>BDB</literal> support by running
+ <literal>BDB</literal> support by invoking
<command>configure</command> with the
<option>--with-berkeley-db</option> option in addition to any
other options that you normally use. Download a MySQL
@@ -3266,18 +3266,19 @@
</para>
<para>
+ The <literal>EXAMPLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-example-storage-engine</option> option.
+ </para>
+
+ <para>
To examine the source for the <literal>EXAMPLE</literal> engine,
look in the <filename>sql/examples</filename> directory of a MySQL
source distribution.
</para>
<para>
- To enable this storage engine, use the
- <option>--with-example-storage-engine</option> option to
- <command>configure</command> when you build MySQL.
- </para>
-
- <para>
When you create an <literal>EXAMPLE</literal> table, the server
creates a table definition file in the database directory. The
file begins with the table name and has an
@@ -3327,8 +3328,10 @@
</para>
<para>
- The <literal>FEDERATED</literal> storage engine is available only
- in the <literal>-Max</literal> version of MySQL.
+ The <literal>FEDERATED</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-federated-storage-engine</option> option.
</para>
<para>
@@ -3720,12 +3723,23 @@
</para>
<para>
- To enable this storage engine, use the
- <option>--with-archive-storage-engine</option> option to
- <command>configure</command> when you build MySQL. You can see if
- this storage engine is available with this statement:
+ The <literal>ARCHIVE</literal> storage engine is included in MySQL
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-archive-storage-engine</option> option.
</para>
+ <para>
+ To examine the source for the <literal>ARCHIVE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
+ You can check whether the <literal>ARCHIVE</literal> storage
+ engine is available with this statement:
+ </para>
+
<programlisting>
mysql> <userinput>SHOW VARIABLES LIKE 'have_archive';</userinput>
</programlisting>
@@ -3855,6 +3869,19 @@
</para>
<para>
+ The <literal>CSV</literal> storage engine is included in MySQL-Max
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-csv-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>CSV</literal> engine, look
+ in the <filename>sql/examples</filename> directory of a MySQL
+ source distribution.
+ </para>
+
+ <para>
When you create a <literal>CSV</literal> table, the server creates
a table definition file in the database directory. The file begins
with the table name and has an <filename>.frm</filename>
@@ -3937,6 +3964,19 @@
</programlisting>
<para>
+ The <literal>BLACKHOLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-blackhole-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>BLACKHOLE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
When you create a <literal>BLACKHOLE</literal> table, the server
creates a table definition file in the database directory. The
file begins with the table name and has an
@@ -3950,16 +3990,14 @@
</para>
<para>
- To enable this storage engine, use the
- <option>--with-blackhole-storage-engine</option> option to
- <command>configure</command> when you build MySQL. The
- <literal>BLACKHOLE</literal> storage engine is available in
- MySQL-supplied server binaries; you can determine whether or not
- your version supports this engine by viewing the output of
- <literal>SHOW ENGINES</literal> or <literal>SHOW VARIABLES LIKE
- 'have%'</literal>.
+ You can check whether the <literal>BLACKHOLE</literal> storage
+ engine is available with this statement:
</para>
+<programlisting>
+mysql> <userinput>SHOW VARIABLES LIKE 'have_blackhole_engine';</userinput>
+</programlisting>
+
<para>
Inserts into a <literal>BLACKHOLE</literal> table do not store any
data, but if the binary log is enabled, the SQL statements are
Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml 2006-01-13 02:42:20 UTC (rev 792)
+++ trunk/refman-5.1/storage-engines.xml 2006-01-13 02:42:39 UTC (rev 793)
@@ -2595,7 +2595,7 @@
<para>
If you build MySQL from source, you can enable
- <literal>BDB</literal> support by running
+ <literal>BDB</literal> support by invoking
<command>configure</command> with the
<option>--with-berkeley-db</option> option in addition to any
other options that you normally use. Download a MySQL
@@ -3268,18 +3268,19 @@
</para>
<para>
+ The <literal>EXAMPLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-example-storage-engine</option> option.
+ </para>
+
+ <para>
To examine the source for the <literal>EXAMPLE</literal> engine,
look in the <filename>sql/examples</filename> directory of a MySQL
source distribution.
</para>
<para>
- To enable this storage engine, use the
- <option>--with-example-storage-engine</option> option to
- <command>configure</command> when you build MySQL.
- </para>
-
- <para>
When you create an <literal>EXAMPLE</literal> table, the server
creates a table definition file in the database directory. The
file begins with the table name and has an
@@ -3328,8 +3329,10 @@
</para>
<para>
- The <literal>FEDERATED</literal> storage engine is available only
- in the <literal>-Max</literal> version of MySQL.
+ The <literal>FEDERATED</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-federated-storage-engine</option> option.
</para>
<para>
@@ -3723,12 +3726,23 @@
</para>
<para>
- To enable this storage engine, use the
- <option>--with-archive-storage-engine</option> option to
- <command>configure</command> when you build MySQL. You can see if
- this storage engine is available with this statement:
+ The <literal>ARCHIVE</literal> storage engine is included in MySQL
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-archive-storage-engine</option> option.
</para>
+ <para>
+ To examine the source for the <literal>ARCHIVE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
+ You can check whether the <literal>ARCHIVE</literal> storage
+ engine is available with this statement:
+ </para>
+
<programlisting>
mysql> <userinput>SHOW VARIABLES LIKE 'have_archive';</userinput>
</programlisting>
@@ -3870,6 +3884,19 @@
</para>
<para>
+ The <literal>CSV</literal> storage engine is included in MySQL-Max
+ binary distributions. To enable this storage engine if you build
+ MySQL from source, invoke <command>configure</command> with the
+ <option>--with-csv-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>CSV</literal> engine, look
+ in the <filename>sql/examples</filename> directory of a MySQL
+ source distribution.
+ </para>
+
+ <para>
When you create a <literal>CSV</literal> table, the server creates
a table definition file in the database directory. The file begins
with the table name and has an <filename>.frm</filename>
@@ -3952,6 +3979,19 @@
</programlisting>
<para>
+ The <literal>BLACKHOLE</literal> storage engine is included in
+ MySQL-Max binary distributions. To enable this storage engine if
+ you build MySQL from source, invoke <command>configure</command>
+ with the <option>--with-blackhole-storage-engine</option> option.
+ </para>
+
+ <para>
+ To examine the source for the <literal>BLACKHOLE</literal> engine,
+ look in the <filename>sql</filename> directory of a MySQL source
+ distribution.
+ </para>
+
+ <para>
When you create a <literal>BLACKHOLE</literal> table, the server
creates a table definition file in the database directory. The
file begins with the table name and has an
@@ -3965,16 +4005,14 @@
</para>
<para>
- To enable this storage engine, use the
- <option>--with-blackhole-storage-engine</option> option to
- <command>configure</command> when you build MySQL. The
- <literal>BLACKHOLE</literal> storage engine is available in
- MySQL-supplied server binaries; you can determine whether or not
- your version supports this engine by viewing the output of
- <literal>SHOW ENGINES</literal> or <literal>SHOW VARIABLES LIKE
- 'have%'</literal>.
+ You can check whether the <literal>BLACKHOLE</literal> storage
+ engine is available with this statement:
</para>
+<programlisting>
+mysql> <userinput>SHOW VARIABLES LIKE 'have_blackhole_engine';</userinput>
+</programlisting>
+
<para>
Inserts into a <literal>BLACKHOLE</literal> table do not store any
data, but if the binary log is enabled, the SQL statements are
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r793 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 13 Jan |
