Author: paul
Date: 2006-01-12 21:22:51 +0100 (Thu, 12 Jan 2006)
New Revision: 782
Log:
r6125@frost: paul | 2006-01-12 14:22:19 -0600
General revisions.
Modified:
trunk/
trunk/refman-4.1/database-administration.xml
trunk/refman-4.1/storage-engines.xml
trunk/refman-5.0/database-administration.xml
trunk/refman-5.0/storage-engines.xml
trunk/refman-5.1/database-administration.xml
trunk/refman-5.1/storage-engines.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6124
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6125
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-4.1/database-administration.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -3700,6 +3700,10 @@
<para>
(New in MySQL 4.0.0)
</para>
+
+ <para>
+ See <xref linkend="myisam-start"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-4.1/storage-engines.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -756,7 +756,8 @@
<para>
The following options to <command>mysqld</command> can be used
- to change the behavior of <literal>MyISAM</literal> tables:
+ to change the behavior of <literal>MyISAM</literal> tables. For
+ additional information, see <xref linkend="server-options"/>.
</para>
<itemizedlist>
@@ -784,27 +785,21 @@
<para>
<emphasis role="bold">Note</emphasis>: If you do this, you
- should not use <literal>MyISAM</literal> tables from another
- program (such as from another MySQL server or with
- <command>myisamchk</command>) when the table is in use.
- Doing so leads to index corruption.
+ should not access <literal>MyISAM</literal> tables from
+ another program (such as from another MySQL server or with
+ <command>myisamchk</command>) when the tables are in use.
+ Doing so risks index corruption. Using
+ <option>--external-locking</option> does not eliminate this
+ risk.
</para>
-
- <para>
- Using <option>--external-locking</option> does not help for
- tables that use <option>--delay-key-write</option>.
- </para>
</listitem>
</itemizedlist>
<para>
- See <xref linkend="server-options"/>.
- </para>
-
- <para>
The following system variables affect the behavior of
- <literal>MyISAM</literal> tables:
+ <literal>MyISAM</literal> tables. For additional information,
+ see <xref linkend="server-system-variables"/>.
</para>
<itemizedlist>
@@ -862,10 +857,6 @@
</itemizedlist>
<para>
- See <xref linkend="server-system-variables"/>.
- </para>
-
- <para>
Automatic recovery is activated if you start
<command>mysqld</command> with the
<option>--myisam-recover</option> option. In this case, when the
@@ -880,7 +871,7 @@
<listitem>
<para>
- The table is checked for errors.
+ The server checks the table for errors.
</para>
</listitem>
@@ -911,8 +902,8 @@
</itemizedlist>
<para>
- If the recovery wouldn't be able to recover all rows from a
- previous completed statement and you didn't specify
+ If the recovery wouldn't be able to recover all rows from
+ previously completed statementas and you didn't specify
<literal>FORCE</literal> in the value of the
<option>--myisam-recover</option> option, automatic repair
aborts with an error message in the error log:
@@ -963,7 +954,7 @@
<para>
String indexes are space compressed. If the first index part is
a string, it is also prefix compressed. Space compression makes
- the index file smaller than the worst-case figure if the string
+ the index file smaller than the worst-case figure if a string
column has a lot of trailing space or is a
<literal>VARCHAR</literal> column that is not always used to the
full length. Prefix compression is used on keys that start with
@@ -973,10 +964,11 @@
<para>
In <literal>MyISAM</literal> tables, you can also prefix
- compress numbers by specifying <literal>PACK_KEYS=1</literal>
- when you create the table. This helps when you have many integer
- keys that have an identical prefix when the numbers are stored
- high-byte first.
+ compress numbers by specifying the
+ <literal>PACK_KEYS=1</literal> table option when you create the
+ table. Numbers are stored with the high byte first, so this
+ helps when you have many integer keys that have an identical
+ prefix.
</para>
</section>
@@ -987,22 +979,24 @@
<para>
<literal>MyISAM</literal> supports three different storage
- formats. Two of them (fixed and dynamic format) are chosen
+ formats. Two of them, fixed and dynamic format, are chosen
automatically depending on the type of columns you are using.
The third, compressed format, can be created only with the
<command>myisampack</command> utility.
</para>
<para>
- When you <literal>CREATE</literal> or <literal>ALTER</literal> a
- table that has no <literal>BLOB</literal> or
- <literal>TEXT</literal> columns, you can force the table format
- to <literal>FIXED</literal> or <literal>DYNAMIC</literal> with
- the <literal>ROW_FORMAT</literal> table option. This causes
+ When you use <literal>CREATE TABLE</literal> or <literal>ALTER
+ TABLE</literal> for a table that has no <literal>BLOB</literal>
+ or <literal>TEXT</literal> columns, you can force the table
+ format to <literal>FIXED</literal> or <literal>DYNAMIC</literal>
+ with the <literal>ROW_FORMAT</literal> table option. This causes
<literal>CHAR</literal> and <literal>VARCHAR</literal> columns
to become <literal>CHAR</literal> for <literal>FIXED</literal>
format, or <literal>VARCHAR</literal> for
- <literal>DYNAMIC</literal> format.
+ <literal>DYNAMIC</literal> format. See
+ <xref linkend="create-table"/>, for information about
+ <literal>ROW_FORMAT</literal>.
</para>
<section id="static-format">
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-5.0/database-administration.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -3712,6 +3712,10 @@
old data file as a backup so that you can later examine
what happened.
</para>
+
+ <para>
+ See <xref linkend="myisam-start"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-5.0/storage-engines.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -772,7 +772,8 @@
<para>
The following options to <command>mysqld</command> can be used
- to change the behavior of <literal>MyISAM</literal> tables:
+ to change the behavior of <literal>MyISAM</literal> tables. For
+ additional information, see <xref linkend="server-options"/>.
</para>
<itemizedlist>
@@ -800,27 +801,21 @@
<para>
<emphasis role="bold">Note</emphasis>: If you do this, you
- should not use <literal>MyISAM</literal> tables from another
- program (such as from another MySQL server or with
- <command>myisamchk</command>) when the table is in use.
- Doing so leads to index corruption.
+ should not access <literal>MyISAM</literal> tables from
+ another program (such as from another MySQL server or with
+ <command>myisamchk</command>) when the tables are in use.
+ Doing so risks index corruption. Using
+ <option>--external-locking</option> does not eliminate this
+ risk.
</para>
-
- <para>
- Using <option>--external-locking</option> does not help for
- tables that use <option>--delay-key-write</option>.
- </para>
</listitem>
</itemizedlist>
<para>
- See <xref linkend="server-options"/>.
- </para>
-
- <para>
The following system variables affect the behavior of
- <literal>MyISAM</literal> tables:
+ <literal>MyISAM</literal> tables. For additional information,
+ see <xref linkend="server-system-variables"/>.
</para>
<itemizedlist>
@@ -876,10 +871,6 @@
</itemizedlist>
<para>
- See <xref linkend="server-system-variables"/>.
- </para>
-
- <para>
Automatic recovery is activated if you start
<command>mysqld</command> with the
<option>--myisam-recover</option> option. In this case, when the
@@ -894,7 +885,7 @@
<listitem>
<para>
- The table is checked for errors.
+ The server checks the table for errors.
</para>
</listitem>
@@ -925,8 +916,8 @@
</itemizedlist>
<para>
- If the recovery wouldn't be able to recover all rows from a
- previous completed statement and you didn't specify
+ If the recovery wouldn't be able to recover all rows from
+ previously completed statementas and you didn't specify
<literal>FORCE</literal> in the value of the
<option>--myisam-recover</option> option, automatic repair
aborts with an error message in the error log:
@@ -977,7 +968,7 @@
<para>
String indexes are space compressed. If the first index part is
a string, it is also prefix compressed. Space compression makes
- the index file smaller than the worst-case figure if the string
+ the index file smaller than the worst-case figure if a string
column has a lot of trailing space or is a
<literal>VARCHAR</literal> column that is not always used to the
full length. Prefix compression is used on keys that start with
@@ -987,10 +978,11 @@
<para>
In <literal>MyISAM</literal> tables, you can also prefix
- compress numbers by specifying <literal>PACK_KEYS=1</literal>
- when you create the table. This helps when you have many integer
- keys that have an identical prefix when the numbers are stored
- high-byte first.
+ compress numbers by specifying the
+ <literal>PACK_KEYS=1</literal> table option when you create the
+ table. Numbers are stored with the high byte first, so this
+ helps when you have many integer keys that have an identical
+ prefix.
</para>
</section>
@@ -1001,18 +993,18 @@
<para>
<literal>MyISAM</literal> supports three different storage
- formats. Two of them (fixed and dynamic format) are chosen
+ formats. Two of them, fixed and dynamic format, are chosen
automatically depending on the type of columns you are using.
The third, compressed format, can be created only with the
<command>myisampack</command> utility.
</para>
<para>
- When you <literal>CREATE</literal> or <literal>ALTER</literal> a
- table that has no <literal>BLOB</literal> or
- <literal>TEXT</literal> columns, you can force the table format
- to <literal>FIXED</literal> or <literal>DYNAMIC</literal> with
- the <literal>ROW_FORMAT</literal> table option. This causes
+ When you use <literal>CREATE TABLE</literal> or <literal>ALTER
+ TABLE</literal> for a table that has no <literal>BLOB</literal>
+ or <literal>TEXT</literal> columns, you can force the table
+ format to <literal>FIXED</literal> or <literal>DYNAMIC</literal>
+ with the <literal>ROW_FORMAT</literal> table option. This causes
<literal>CHAR</literal> and <literal>VARCHAR</literal> columns
to become <literal>CHAR</literal> for <literal>FIXED</literal>
format, or <literal>VARCHAR</literal> for
@@ -1022,10 +1014,14 @@
<para>
You can compress or decompress tables by specifying
<literal>ROW_FORMAT={COMPRESSED | DEFAULT}</literal> with
- <literal>ALTER TABLE</literal>. See
- <xref linkend="create-table"/>.
+ <literal>ALTER TABLE</literal>.
</para>
+ <para>
+ See <xref linkend="create-table"/>, for information about
+ <literal>ROW_FORMAT</literal>.
+ </para>
+
<section id="static-format">
<title>&title-static-format;</title>
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-5.1/database-administration.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -3667,6 +3667,10 @@
old data file as a backup so that you can later examine
what happened.
</para>
+
+ <para>
+ See <xref linkend="myisam-start"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml 2006-01-12 20:22:33 UTC (rev 781)
+++ trunk/refman-5.1/storage-engines.xml 2006-01-12 20:22:51 UTC (rev 782)
@@ -767,7 +767,8 @@
<para>
The following options to <command>mysqld</command> can be used
- to change the behavior of <literal>MyISAM</literal> tables:
+ to change the behavior of <literal>MyISAM</literal> tables. For
+ additional information, see <xref linkend="server-options"/>.
</para>
<itemizedlist>
@@ -795,27 +796,21 @@
<para>
<emphasis role="bold">Note</emphasis>: If you do this, you
- should not use <literal>MyISAM</literal> tables from another
- program (such as from another MySQL server or with
- <command>myisamchk</command>) when the table is in use.
- Doing so leads to index corruption.
+ should not access <literal>MyISAM</literal> tables from
+ another program (such as from another MySQL server or with
+ <command>myisamchk</command>) when the tables are in use.
+ Doing so risks index corruption. Using
+ <option>--external-locking</option> does not eliminate this
+ risk.
</para>
-
- <para>
- Using <option>--external-locking</option> does not help for
- tables that use <option>--delay-key-write</option>.
- </para>
</listitem>
</itemizedlist>
<para>
- See <xref linkend="server-options"/>.
- </para>
-
- <para>
The following system variables affect the behavior of
- <literal>MyISAM</literal> tables:
+ <literal>MyISAM</literal> tables. For additional information,
+ see <xref linkend="server-system-variables"/>.
</para>
<itemizedlist>
@@ -834,17 +829,6 @@
<listitem>
<para>
- (<emphasis>OBSOLETE</emphasis>)
- <literal>myisam_max_extra_sort_file_size</literal>
- </para>
-
- <para>
- This parameter is no longer used in MySQL.
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>myisam_max_sort_file_size</literal>
</para>
@@ -869,10 +853,6 @@
</itemizedlist>
<para>
- See <xref linkend="server-system-variables"/>.
- </para>
-
- <para>
Automatic recovery is activated if you start
<command>mysqld</command> with the
<option>--myisam-recover</option> option. In this case, when the
@@ -887,7 +867,7 @@
<listitem>
<para>
- The table is checked for errors.
+ The server checks the table for errors.
</para>
</listitem>
@@ -918,8 +898,8 @@
</itemizedlist>
<para>
- If the recovery wouldn't be able to recover all rows from a
- previous completed statement and you didn't specify
+ If the recovery wouldn't be able to recover all rows from
+ previously completed statementas and you didn't specify
<literal>FORCE</literal> in the value of the
<option>--myisam-recover</option> option, automatic repair
aborts with an error message in the error log:
@@ -970,7 +950,7 @@
<para>
String indexes are space compressed. If the first index part is
a string, it is also prefix compressed. Space compression makes
- the index file smaller than the worst-case figure if the string
+ the index file smaller than the worst-case figure if a string
column has a lot of trailing space or is a
<literal>VARCHAR</literal> column that is not always used to the
full length. Prefix compression is used on keys that start with
@@ -980,10 +960,11 @@
<para>
In <literal>MyISAM</literal> tables, you can also prefix
- compress numbers by specifying <literal>PACK_KEYS=1</literal>
- when you create the table. This helps when you have many integer
- keys that have an identical prefix when the numbers are stored
- high-byte first.
+ compress numbers by specifying the
+ <literal>PACK_KEYS=1</literal> table option when you create the
+ table. Numbers are stored with the high byte first, so this
+ helps when you have many integer keys that have an identical
+ prefix.
</para>
</section>
@@ -994,31 +975,31 @@
<para>
<literal>MyISAM</literal> supports three different storage
- formats. Two of them (fixed and dynamic format) are chosen
+ formats. Two of them, fixed and dynamic format, are chosen
automatically depending on the type of columns you are using.
The third, compressed format, can be created only with the
<command>myisampack</command> utility.
</para>
<para>
- When you <literal>CREATE</literal> or <literal>ALTER</literal> a
- table that has no <literal>BLOB</literal> or
- <literal>TEXT</literal> columns, you can force the table format
- to <literal>FIXED</literal> or <literal>DYNAMIC</literal> with
- the <literal>ROW_FORMAT</literal> table option. This causes
- <literal>CHAR</literal> and <literal>VARCHAR</literal> columns
- to become <literal>CHAR</literal> for <literal>FIXED</literal>
- format, or <literal>VARCHAR</literal> for
- <literal>DYNAMIC</literal> format.
+ When you use <literal>CREATE TABLE</literal> or <literal>ALTER
+ TABLE</literal> for a table that has no <literal>BLOB</literal>
+ or <literal>TEXT</literal> columns, you can force the table
+ format to <literal>FIXED</literal> or <literal>DYNAMIC</literal>
+ with the <literal>ROW_FORMAT</literal> table option.
</para>
<para>
You can compress or decompress tables by specifying
<literal>ROW_FORMAT={COMPRESSED | DEFAULT}</literal> with
- <literal>ALTER TABLE</literal>. See
- <xref linkend="create-table"/>.
+ <literal>ALTER TABLE</literal>.
</para>
+ <para>
+ See <xref linkend="create-table"/>, for information about
+ <literal>ROW_FORMAT</literal>.
+ </para>
+
<section id="static-format">
<title>&title-static-format;</title>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r782 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 12 Jan |
