List:Commits« Previous MessageNext Message »
From:paul Date:January 12 2006 8:22pm
Subject:svn commit - mysqldoc@docsrva: r781 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-common
View as plain text  
Author: paul
Date: 2006-01-12 21:22:33 +0100 (Thu, 12 Jan 2006)
New Revision: 781

Log:
 r6124@frost:  paul | 2006-01-12 13:57:47 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/innodb.xml
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-4.1/problems.xml
   trunk/refman-4.1/spatial-extensions.xml
   trunk/refman-4.1/storage-engines.xml
   trunk/refman-5.0/innodb.xml
   trunk/refman-5.0/ndbcluster.xml
   trunk/refman-5.0/problems.xml
   trunk/refman-5.0/spatial-extensions.xml
   trunk/refman-5.0/storage-engines.xml
   trunk/refman-5.1/custom-engine.xml
   trunk/refman-5.1/innodb.xml
   trunk/refman-5.1/ndbcluster.xml
   trunk/refman-5.1/partitioning.xml
   trunk/refman-5.1/problems.xml
   trunk/refman-5.1/spatial-extensions.xml
   trunk/refman-5.1/storage-engines.xml
   trunk/refman-common/titles.en.ent


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6122
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6124
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2101

Modified: trunk/refman-4.1/innodb.xml
===================================================================
--- trunk/refman-4.1/innodb.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-4.1/innodb.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -114,8 +114,7 @@
 
     <para>
       A forum dedicated to the <literal>InnoDB</literal> storage engine
-      is available at
-      <ulink url="http://forums.mysql.com/list.php?22"/>.
+      is available at <ulink url="&base-url-forum-list;?22"/>.
     </para>
 
   </section>

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-4.1/ndbcluster.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -52,37 +52,44 @@
   </para>
 
   <para>
-    You may wish to make use of two additional online resources provided
-    by MySQL AB:
+    <emphasis role="bold">Additional resources</emphasis>
   </para>
 
   <itemizedlist>
 
     <listitem>
       <para>
-        the MySQL Cluster
-        <ulink url="http://lists.mysql.com/cluster">mailing
-        list</ulink>.
+        Answers to some commonly asked questions about Cluster may be
+        found in the <xref linkend="mysql-cluster-faq"/>.
       </para>
     </listitem>
 
     <listitem>
       <para>
-        the <ulink url="http://forums.mysql.com/list.php?25">Cluster
-        topic area</ulink> on the MySQL User Forums.
+        The MySQL Cluster mailing list:
+        <ulink url="http://lists.mysql.com/cluster"/>.
       </para>
     </listitem>
 
+    <listitem>
+      <para>
+        The MySQL Cluster forum:
+        <ulink url="&base-url-forum-list;?25"/>.
+      </para>
+    </listitem>
+
+    <listitem>
+      <para>
+        If you are new to MySQL Cluster, you may find our Developer Zone
+        article
+        <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">
+        How to set up a MySQL Cluster for two servers</ulink> to be
+        helpful.
+      </para>
+    </listitem>
+
   </itemizedlist>
 
-  <para>
-    Answers to some commonly asked questions about Cluster may be found
-    in the <xref linkend="mysql-cluster-faq"/>. If you are new to MySQL
-    Cluster, you may also find our Developer Zone article
-    <ulink url="http://dev.mysql.com/tech-resources/articles/mysql-cluster-for-two-servers.html">How
-    to set up a MySQL Cluster for two servers</ulink> to be helpful.
-  </para>
-
   <section id="mysql-cluster-overview">
 
     <title>&title-mysql-cluster-overview;</title>

Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-4.1/problems.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -775,7 +775,7 @@
         library. This is beyond the scope of this Manual; consult the
         PHP documentation for more information. You also be able to
         obtain assistance with these issues in our
-        <ulink url="http://forums.mysql.com/list.php?52">MySQL with PHP
+        <ulink url="&base-url-forum-list;?52">MySQL with PHP
         forum</ulink>.
       </para>
 

Modified: trunk/refman-4.1/spatial-extensions.xml
===================================================================
--- trunk/refman-4.1/spatial-extensions.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-4.1/spatial-extensions.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -66,9 +66,8 @@
 
   <para>
     If you have questions or concerns about the use of the spatial
-    extensions to MySQL, you can discuss these in the
-    <ulink url="http://forums.mysql.com/list.php?23">GIS forums</ulink>
-    on our Web site.
+    extensions to MySQL, you can discuss these in the GIS forum:
+    <ulink url="&base-url-forum-list;?23"/>.
   </para>
 
   <section id="gis-introduction">

Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-4.1/storage-engines.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -526,17 +526,24 @@
         </para>
 
         <para>
-          There is no big speed penalty for storing data low byte first;
-          the bytes in a table row normally are unaligned and it doesn't
-          take that much more power to read an unaligned byte in order
-          than in reverse order. Also, the code in the server that
-          fetches column values is not time critical compared to other
-          code.
+          There is no significant speed penalty for storing data low
+          byte first; the bytes in a table row normally are unaligned
+          and it takes little more processing to read an unaligned byte
+          in order than in reverse order. Also, the code in the server
+          that fetches column values is not time critical compared to
+          other code.
         </para>
       </listitem>
 
       <listitem>
         <para>
+          All numeric key values are stored with the high byte first to
+          allow better index compression.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Large files (up to 63-bit file length) are supported on
           filesystems and operating systems that support large files.
         </para>
@@ -554,43 +561,22 @@
       <listitem>
         <para>
           The maximum number of indexes per table is 64 (32 before MySQL
-          4.1.2). This can be changed by recompiling. The maximum number
-          of columns per index is 16.
+          4.1.2). This can be changed by changing the source and
+          recompiling. The maximum number of columns per index is 16.
         </para>
       </listitem>
 
       <listitem>
         <para>
           The maximum key length is 1000 bytes (500 before MySQL 4.1.2).
-          This can be changed by recompiling. For the case of a key
-          longer than 250 bytes, a larger key block size than the
-          default of 1024 bytes is used.
+          This can be changed by changing the source and recompiling.
+          For the case of a key longer than 250 bytes, a larger key
+          block size than the default of 1024 bytes is used.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>BLOB</literal> and <literal>TEXT</literal> columns
-          can be indexed.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>NULL</literal> values are allowed in indexed columns.
-          This takes 0-1 bytes per key.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          All numeric key values are stored with the high byte first to
-          allow better index compression.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           Index files are usually much smaller with
           <literal>MyISAM</literal> than with <literal>ISAM</literal>.
           This means that <literal>MyISAM</literal> normally uses less
@@ -611,13 +597,14 @@
       <listitem>
         <para>
           Internal handling of one <literal>AUTO_INCREMENT</literal>
-          column per table. <literal>MyISAM</literal> automatically
-          updates this column for <literal>INSERT/UPDATE</literal>. This
-          makes <literal>AUTO_INCREMENT</literal> columns faster (at
-          least 10%). Values at the top of the sequence are not reused
-          after being deleted as they are with <literal>ISAM</literal>.
-          (When an <literal>AUTO_INCREMENT</literal> column is defined
-          as the last column of a multiple-column index, reuse of values
+          column per table is supported. <literal>MyISAM</literal>
+          automatically updates this column for
+          <literal>INSERT/UPDATE</literal>. This makes
+          <literal>AUTO_INCREMENT</literal> columns faster (at least
+          10%). Values at the top of the sequence are not reused after
+          being deleted as they are with <literal>ISAM</literal>. (When
+          an <literal>AUTO_INCREMENT</literal> column is defined as the
+          last column of a multiple-column index, reuse of values
           deleted from the top of a sequence does occur.) The
           <literal>AUTO_INCREMENT</literal> value can be reset with
           <literal>ALTER TABLE</literal> or
@@ -627,6 +614,15 @@
 
       <listitem>
         <para>
+          Dynamic-sized rows are much less fragmented when mixing
+          deletes with updates and inserts. This is done by
+          automatically combining adjacent deleted blocks and by
+          extending blocks if the next block is deleted.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           If a table has no free blocks in the middle of the data file,
           you can <literal>INSERT</literal> new rows into it at the same
           time that other threads are reading from the table. (These are
@@ -650,6 +646,20 @@
 
       <listitem>
         <para>
+          <literal>BLOB</literal> and <literal>TEXT</literal> columns
+          can be indexed.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NULL</literal> values are allowed in indexed columns.
+          This takes 0-1 bytes per key.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           As of MySQL 4.1, each character column can have a different
           character set.
         </para>
@@ -705,21 +715,21 @@
         <para>
           Support for a true <literal>VARCHAR</literal> type; a
           <literal>VARCHAR</literal> column starts with a length stored
-          in two bytes.
+          in one or two bytes.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Tables with <literal>VARCHAR</literal> may have fixed or
-          dynamic row length.
+          Tables with <literal>VARCHAR</literal> columns may have fixed
+          or dynamic row length.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>VARCHAR</literal> and <literal>CHAR</literal> columns
-          may be up to 64KB.
+          The sum of the lengths of the <literal>VARCHAR</literal> and
+          <literal>CHAR</literal> columns in a table may be up to 64KB.
         </para>
       </listitem>
 
@@ -736,9 +746,8 @@
     </itemizedlist>
 
     <para>
-      For the <literal>MyISAM</literal> storage engine, there's a
-      dedicated forum available on
-      <ulink url="http://forums.mysql.com/list.php?21"/>.
+      A forum dedicated to the <literal>MyISAM</literal> storage engine
+      is available at <ulink url="&base-url-forum-list;?21"/>.
     </para>
 
     <section id="myisam-start">
@@ -2077,9 +2086,8 @@
       </itemizedlist>
 
       <para>
-        For the <literal>MERGE</literal> storage engine, there's a
-        dedicated forum available on
-        <ulink url="http://forums.mysql.com/list.php?93"/>.
+        A forum dedicated to the <literal>MERGE</literal> storage engine
+        is available at <ulink url="&base-url-forum-list;?93"/>.
       </para>
 
     </section>
@@ -2413,9 +2421,8 @@
     </itemizedlist>
 
     <para>
-      For the <literal>MEMORY</literal> storage engine, there's a
-      dedicated forum available on
-      <ulink url="http://forums.mysql.com/list.php?92"/>.
+      A forum dedicated to the <literal>MEMORY</literal> storage engine
+      is available at <ulink url="&base-url-forum-list;?92"/>.
     </para>
 
   </section>
@@ -3457,9 +3464,8 @@
     </para>
 
     <para>
-      For the <literal>ARCHIVE</literal> storage engine, there's a
-      dedicated forum available on
-      <ulink url="http://forums.mysql.com/list.php?112"/>.
+      A forum dedicated to the <literal>ARCHIVE</literal> storage engine
+      is available at <ulink url="&base-url-forum-list;?112"/>.
     </para>
 
   </section>

Modified: trunk/refman-5.0/innodb.xml
===================================================================
--- trunk/refman-5.0/innodb.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.0/innodb.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -120,7 +120,7 @@
         <para>
           A forum dedicated to the <literal>InnoDB</literal> storage
           engine is available at
-          <ulink url="http://forums.mysql.com/list.php?22"/>.
+          <ulink url="&base-url-forum-list;?22"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.0/ndbcluster.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -73,7 +73,7 @@
     <listitem>
       <para>
         The MySQL Cluster forum:
-        <ulink url="http://forums.mysql.com/list.php?25"/>.
+        <ulink url="&base-url-forum-list;?25"/>.
       </para>
     </listitem>
 

Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.0/problems.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -775,7 +775,7 @@
         library. This is beyond the scope of this Manual; consult the
         PHP documentation for more information. You also be able to
         obtain assistance with these issues in our
-        <ulink url="http://forums.mysql.com/list.php?52">MySQL with PHP
+        <ulink url="&base-url-forum-list;?52">MySQL with PHP
         forum</ulink>.
       </para>
 

Modified: trunk/refman-5.0/spatial-extensions.xml
===================================================================
--- trunk/refman-5.0/spatial-extensions.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.0/spatial-extensions.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -78,8 +78,8 @@
       <listitem>
         <para>
           If you have questions or concerns about the use of the spatial
-          extensions to MySQL, you can discuss these in the GIS forums:
-          <ulink url="http://forums.mysql.com/list.php?23"/>.
+          extensions to MySQL, you can discuss these in the GIS forum:
+          <ulink url="&base-url-forum-list;?23"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.0/storage-engines.xml
===================================================================
--- trunk/refman-5.0/storage-engines.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.0/storage-engines.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -534,17 +534,24 @@
         </para>
 
         <para>
-          There is no big speed penalty for storing data low byte first;
-          the bytes in a table row normally are unaligned and it doesn't
-          take that much more power to read an unaligned byte in order
-          than in reverse order. Also, the code in the server that
-          fetches column values is not time critical compared to other
-          code.
+          There is no significant speed penalty for storing data low
+          byte first; the bytes in a table row normally are unaligned
+          and it takes little more processing to read an unaligned byte
+          in order than in reverse order. Also, the code in the server
+          that fetches column values is not time critical compared to
+          other code.
         </para>
       </listitem>
 
       <listitem>
         <para>
+          All numeric key values are stored with the high byte first to
+          allow better index compression.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Large files (up to 63-bit file length) are supported on
           filesystems and operating systems that support large files.
         </para>
@@ -562,12 +569,14 @@
       <listitem>
         <para>
           The maximum number of indexes per <literal>MyISAM</literal>
-          table is 64. This can be changed by recompiling; beginning
-          with MySQL 5.0.18, you can configure the build using the
-          <option>--with-max-indexes=<replaceable>N</replaceable></option>,
-          where <replaceable>N</replaceable>&le;128 is the maximum
+          table is 64. This can be changed by recompiling. Beginning
+          with MySQL 5.0.18, you can configure the build by invoking
+          <command>configure</command> with the
+          <option>--with-max-indexes=<replaceable>N</replaceable></option>
+          option, where <replaceable>N</replaceable> is the maximum
           number of indexes to permit per <literal>MyISAM</literal>
-          table.
+          table. <replaceable>N</replaceable> must be less thann or
+          equal to 128. Before MySQL 5.0.18, you must change the source.
         </para>
 
         <para>
@@ -578,34 +587,14 @@
       <listitem>
         <para>
           The maximum key length is 1000 bytes. This can also be changed
-          by recompiling. For the case of a key longer than 250 bytes, a
-          larger key block size than the default of 1024 bytes is used.
+          by changing the source and recompiling. For the case of a key
+          longer than 250 bytes, a larger key block size than the
+          default of 1024 bytes is used.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>BLOB</literal> and <literal>TEXT</literal> columns
-          can be indexed.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>NULL</literal> values are allowed in indexed columns.
-          This takes 0-1 bytes per key.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          All numeric key values are stored with the high byte first to
-          allow better index compression.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           When rows are inserted in sorted order (as when you are using
           an <literal>AUTO_INCREMENT</literal> column), the index tree
           is split so that the high node only contains one key. This
@@ -616,22 +605,32 @@
       <listitem>
         <para>
           Internal handling of one <literal>AUTO_INCREMENT</literal>
-          column per table. <literal>MyISAM</literal> automatically
-          updates this column for <literal>INSERT</literal>and
-          <literal>UPDATE</literal> operations. This makes
-          <literal>AUTO_INCREMENT</literal> columns faster (at least
-          10%). Values at the top of the sequence are not reused after
-          being deleted. (When an <literal>AUTO_INCREMENT</literal>
-          column is defined as the last column of a multiple-column
-          index, reuse of values deleted from the top of a sequence does
-          occur.) The <literal>AUTO_INCREMENT</literal> value can be
-          reset with <literal>ALTER TABLE</literal> or
+          column per table is supported. <literal>MyISAM</literal>
+          automatically updates this column for
+          <literal>INSERT</literal> and <literal>UPDATE</literal>
+          operations. This makes <literal>AUTO_INCREMENT</literal>
+          columns faster (at least 10%). Values at the top of the
+          sequence are not reused after being deleted. (When an
+          <literal>AUTO_INCREMENT</literal> column is defined as the
+          last column of a multiple-column index, reuse of values
+          deleted from the top of a sequence does occur.) The
+          <literal>AUTO_INCREMENT</literal> value can be reset with
+          <literal>ALTER TABLE</literal> or
           <command>myisamchk</command>.
         </para>
       </listitem>
 
       <listitem>
         <para>
+          Dynamic-sized rows are much less fragmented when mixing
+          deletes with updates and inserts. This is done by
+          automatically combining adjacent deleted blocks and by
+          extending blocks if the next block is deleted.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           If a table has no free blocks in the middle of the data file,
           you can <literal>INSERT</literal> new rows into it at the same
           time that other threads are reading from the table. (These are
@@ -655,6 +654,20 @@
 
       <listitem>
         <para>
+          <literal>BLOB</literal> and <literal>TEXT</literal> columns
+          can be indexed.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NULL</literal> values are allowed in indexed columns.
+          This takes 0&minus;1 bytes per key.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Each character column can have a different character set. See
           <xref linkend="charset"/>.
         </para>
@@ -707,21 +720,21 @@
         <para>
           Support for a true <literal>VARCHAR</literal> type; a
           <literal>VARCHAR</literal> column starts with a length stored
-          in two bytes.
+          in one or two bytes.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Tables with <literal>VARCHAR</literal> may have fixed or
-          dynamic row length.
+          Tables with <literal>VARCHAR</literal> columns may have fixed
+          or dynamic row length.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>VARCHAR</literal> and <literal>CHAR</literal> columns
-          may be up to 64KB.
+          The sum of the lengths of the <literal>VARCHAR</literal> and
+          <literal>CHAR</literal> columns in a table may be up to 64KB.
         </para>
       </listitem>
 
@@ -745,9 +758,9 @@
 
       <listitem>
         <para>
-          For the <literal>MyISAM</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?21"/>.
+          A forum dedicated to the <literal>MyISAM</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?21"/>.
         </para>
       </listitem>
 
@@ -2055,9 +2068,9 @@
 
         <listitem>
           <para>
-            For the <literal>MERGE</literal> storage engine, there's a
-            dedicated forum available on
-            <ulink url="http://forums.mysql.com/list.php?93"/>.
+            A forum dedicated to the <literal>MERGE</literal> storage
+            engine is available at
+            <ulink url="&base-url-forum-list;?93"/>.
           </para>
         </listitem>
 
@@ -2386,9 +2399,9 @@
 
       <listitem>
         <para>
-          For the <literal>MEMORY</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?92"/>.
+          A forum dedicated to the <literal>MEMORY</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?92"/>.
         </para>
       </listitem>
 
@@ -3361,9 +3374,9 @@
 
       <listitem>
         <para>
-          For the <literal>FEDERATED</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?105"/>.
+          A forum dedicated to the <literal>FEDERATED</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?105"/>.
         </para>
       </listitem>
 
@@ -3609,18 +3622,6 @@
         <emphasis role="bold">Additional resources</emphasis>
       </para>
 
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            For the <literal>FEDERATED</literal> storage engine, there's
-            a dedicated forum available on
-            <ulink url="http://forums.mysql.com/list.php?105"/>.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
     </section>
 
     <section id="federated-limitations">
@@ -3857,9 +3858,9 @@
 
       <listitem>
         <para>
-          For the <literal>ARCHIVE</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?112"/>.
+          A forum dedicated to the <literal>ARCHIVE</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?112"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/custom-engine.xml
===================================================================
--- trunk/refman-5.1/custom-engine.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/custom-engine.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -45,8 +45,8 @@
 
       <listitem>
         <para>
-          There is a forum dedicated to custom storage engines available
-          on <ulink url="http://forums.mysql.com/list.php?94"/>.
+          A forum dedicated to custom storage engines is available at
+          <ulink url="&base-url-forum-list;?94"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/innodb.xml
===================================================================
--- trunk/refman-5.1/innodb.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/innodb.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -120,7 +120,7 @@
         <para>
           A forum dedicated to the <literal>InnoDB</literal> storage
           engine is available at
-          <ulink url="http://forums.mysql.com/list.php?22"/>.
+          <ulink url="&base-url-forum-list;?22"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/ndbcluster.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -73,7 +73,7 @@
     <listitem>
       <para>
         The MySQL Cluster forum:
-        <ulink url="http://forums.mysql.com/list.php?25"/>.
+        <ulink url="&base-url-forum-list;?25"/>.
       </para>
     </listitem>
 

Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/partitioning.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -56,8 +56,8 @@
 
     <listitem>
       <para>
-        <ulink url="http://forums.mysql.com/list.php?106">MySQL
-        Partitioning Forum</ulink>
+        <ulink url="&base-url-forum-list;?106">MySQL Partitioning
+        Forum</ulink>
       </para>
 
       <para>
@@ -127,7 +127,7 @@
     <option>--with-partition</option> option. For more information about
     building MySQL, see <xref linkend="installing-source"/>. If you have
     problems compiling a partitioning-enabled MySQL 5.1 build, check the
-    <ulink url="http://forums.mysql.com/list.php?106">MySQL Partitioning
+    <ulink url="&base-url-forum-list;?106">MySQL Partitioning
     Forum</ulink> and ask for assistance there if you don't find a
     solution to your problem already posted.
   </para>

Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/problems.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -775,7 +775,7 @@
         library. This is beyond the scope of this Manual; consult the
         PHP documentation for more information. You also be able to
         obtain assistance with these issues in our
-        <ulink url="http://forums.mysql.com/list.php?52">MySQL with PHP
+        <ulink url="&base-url-forum-list;?52">MySQL with PHP
         forum</ulink>.
       </para>
 

Modified: trunk/refman-5.1/spatial-extensions.xml
===================================================================
--- trunk/refman-5.1/spatial-extensions.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/spatial-extensions.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -78,8 +78,8 @@
       <listitem>
         <para>
           If you have questions or concerns about the use of the spatial
-          extensions to MySQL, you can discuss these in the GIS forums:
-          <ulink url="http://forums.mysql.com/list.php?23"/>.
+          extensions to MySQL, you can discuss these in the GIS forum:
+          <ulink url="&base-url-forum-list;?23"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-5.1/storage-engines.xml
===================================================================
--- trunk/refman-5.1/storage-engines.xml	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-5.1/storage-engines.xml	2006-01-12 20:22:33 UTC (rev 781)
@@ -538,40 +538,40 @@
         </para>
 
         <para>
-          There is no big speed penalty for storing data low byte first;
-          the bytes in a table row normally are unaligned and it doesn't
-          take that much more power to read an unaligned byte in order
-          than in reverse order. Also, the code in the server that
-          fetches column values is not time critical compared to other
-          code.
+          There is no significant speed penalty for storing data low
+          byte first; the bytes in a table row normally are unaligned
+          and it takes little more processing to read an unaligned byte
+          in order than in reverse order. Also, the code in the server
+          that fetches column values is not time critical compared to
+          other code.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Large files (up to 63-bit file length) are supported on
-          filesystems and operating systems that support large files.
+          All numeric key values are stored with the high byte first to
+          allow better index compression.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Dynamic-sized rows are much less fragmented when mixing
-          deletes with updates and inserts. This is done by
-          automatically combining adjacent deleted blocks and by
-          extending blocks if the next block is deleted.
+          Large files (up to 63-bit file length) are supported on
+          filesystems and operating systems that support large files.
         </para>
       </listitem>
 
       <listitem>
         <para>
           The maximum number of indexes per <literal>MyISAM</literal>
-          table is 64. This can be changed by recompiling; beginning
-          with MySQL 5.1.4, you can configure the build using the
-          <option>--with-max-indexes=<replaceable>N</replaceable></option>,
-          where <replaceable>N</replaceable>&le;128 is the maximum
+          table is 64. This can be changed by recompiling. Beginning
+          with MySQL 5.1.4, you can configure the build by invoking
+          <command>configure</command> with the
+          <option>--with-max-indexes=<replaceable>N</replaceable></option>
+          option, where <replaceable>N</replaceable> is the maximum
           number of indexes to permit per <literal>MyISAM</literal>
-          table.
+          table. <replaceable>N</replaceable> must be less thann or
+          equal to 128. Before MySQL 5.1.4, you must change the source.
         </para>
 
         <para>
@@ -582,34 +582,14 @@
       <listitem>
         <para>
           The maximum key length is 1000 bytes. This can also be changed
-          by recompiling. For the case of a key longer than 250 bytes, a
-          larger key block size than the default of 1024 bytes is used.
+          by changing the source and recompiling. For the case of a key
+          longer than 250 bytes, a larger key block size than the
+          default of 1024 bytes is used.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>BLOB</literal> and <literal>TEXT</literal> columns
-          can be indexed.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          <literal>NULL</literal> values are allowed in indexed columns.
-          This takes 0-1 bytes per key.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
-          All numeric key values are stored with the high byte first to
-          allow better index compression.
-        </para>
-      </listitem>
-
-      <listitem>
-        <para>
           When rows are inserted in sorted order (as when you are using
           an <literal>AUTO_INCREMENT</literal> column), the index tree
           is split so that the high node only contains one key. This
@@ -620,22 +600,32 @@
       <listitem>
         <para>
           Internal handling of one <literal>AUTO_INCREMENT</literal>
-          column per table. <literal>MyISAM</literal> automatically
-          updates this column for <literal>INSERT</literal>and
-          <literal>UPDATE</literal> operations. This makes
-          <literal>AUTO_INCREMENT</literal> columns faster (at least
-          10%). Values at the top of the sequence are not reused after
-          being deleted. (When an <literal>AUTO_INCREMENT</literal>
-          column is defined as the last column of a multiple-column
-          index, reuse of values deleted from the top of a sequence does
-          occur.) The <literal>AUTO_INCREMENT</literal> value can be
-          reset with <literal>ALTER TABLE</literal> or
+          column per table is supported. <literal>MyISAM</literal>
+          automatically updates this column for
+          <literal>INSERT</literal> and <literal>UPDATE</literal>
+          operations. This makes <literal>AUTO_INCREMENT</literal>
+          columns faster (at least 10%). Values at the top of the
+          sequence are not reused after being deleted. (When an
+          <literal>AUTO_INCREMENT</literal> column is defined as the
+          last column of a multiple-column index, reuse of values
+          deleted from the top of a sequence does occur.) The
+          <literal>AUTO_INCREMENT</literal> value can be reset with
+          <literal>ALTER TABLE</literal> or
           <command>myisamchk</command>.
         </para>
       </listitem>
 
       <listitem>
         <para>
+          Dynamic-sized rows are much less fragmented when mixing
+          deletes with updates and inserts. This is done by
+          automatically combining adjacent deleted blocks and by
+          extending blocks if the next block is deleted.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           If a table has no free blocks in the middle of the data file,
           you can <literal>INSERT</literal> new rows into it at the same
           time that other threads are reading from the table. (These are
@@ -659,6 +649,20 @@
 
       <listitem>
         <para>
+          <literal>BLOB</literal> and <literal>TEXT</literal> columns
+          can be indexed.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
+          <literal>NULL</literal> values are allowed in indexed columns.
+          This takes 0&minus;1 bytes per key.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           Each character column can have a different character set. See
           <xref linkend="charset"/>.
         </para>
@@ -711,21 +715,21 @@
         <para>
           Support for a true <literal>VARCHAR</literal> type; a
           <literal>VARCHAR</literal> column starts with a length stored
-          in two bytes.
+          in one or two bytes.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          Tables with <literal>VARCHAR</literal> may have fixed or
-          dynamic row length.
+          Tables with <literal>VARCHAR</literal> columns may have fixed
+          or dynamic row length.
         </para>
       </listitem>
 
       <listitem>
         <para>
-          <literal>VARCHAR</literal> and <literal>CHAR</literal> columns
-          may be up to 64KB.
+          The sum of the lengths of the <literal>VARCHAR</literal> and
+          <literal>CHAR</literal> columns in a table may be up to 64KB.
         </para>
       </listitem>
 
@@ -749,9 +753,9 @@
 
       <listitem>
         <para>
-          For the <literal>MyISAM</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?21"/>.
+          A forum dedicated to the <literal>MyISAM</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?21"/>.
         </para>
       </listitem>
 
@@ -2055,9 +2059,9 @@
 
         <listitem>
           <para>
-            For the <literal>MERGE</literal> storage engine, there's a
-            dedicated forum available on
-            <ulink url="http://forums.mysql.com/list.php?93"/>.
+            A forum dedicated to the <literal>MERGE</literal> storage
+            engine is available at
+            <ulink url="&base-url-forum-list;?93"/>.
           </para>
         </listitem>
 
@@ -2386,9 +2390,9 @@
 
       <listitem>
         <para>
-          For the <literal>MEMORY</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?92"/>.
+          A forum dedicated to the <literal>MEMORY</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?92"/>.
         </para>
       </listitem>
 
@@ -3386,9 +3390,9 @@
 
       <listitem>
         <para>
-          For the <literal>FEDERATED</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?105"/>.
+          A forum dedicated to the <literal>FEDERATED</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?105"/>.
         </para>
       </listitem>
 
@@ -3636,18 +3640,6 @@
         <emphasis role="bold">Additional resources</emphasis>
       </para>
 
-      <itemizedlist>
-
-        <listitem>
-          <para>
-            For the <literal>FEDERATED</literal> storage engine, there's
-            a dedicated forum available on
-            <ulink url="http://forums.mysql.com/list.php?105"/>.
-          </para>
-        </listitem>
-
-      </itemizedlist>
-
     </section>
 
     <section id="federated-limitations">
@@ -3896,9 +3888,9 @@
 
       <listitem>
         <para>
-          For the <literal>ARCHIVE</literal> storage engine, there's a
-          dedicated forum available on
-          <ulink url="http://forums.mysql.com/list.php?112"/>.
+          A forum dedicated to the <literal>ARCHIVE</literal> storage
+          engine is available at
+          <ulink url="&base-url-forum-list;?112"/>.
         </para>
       </listitem>
 

Modified: trunk/refman-common/titles.en.ent
===================================================================
--- trunk/refman-common/titles.en.ent	2006-01-12 19:15:52 UTC (rev 780)
+++ trunk/refman-common/titles.en.ent	2006-01-12 20:22:33 UTC (rev 781)
@@ -9,6 +9,7 @@
 <!ENTITY base-url-docs "http://dev.mysql.com/doc/">
 <!ENTITY base-url-downloads "http://dev.mysql.com/downloads/">
 <!ENTITY base-url-refman "http://dev.mysql.com/doc/refman">
+<!ENTITY base-url-forum-list "http://forums.mysql.com/list.php">
 <!ENTITY title-access-denied "Causes of <literal>Access denied</literal> Errors">
 <!ENTITY title-access-denied-error "While Connecting, an <literal>Access denied</literal> Error Occurs">
 <!ENTITY title-access-long-tables "I Have Very Long Tables. What is the Best Configuration for MyODBC to Access These Tables?">

Thread
svn commit - mysqldoc@docsrva: r781 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-commonpaul12 Jan