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

[mcbrown]

Author: mcbrown
Date: 2007-01-23 17:11:51 +0100 (Tue, 23 Jan 2007)
New Revision: 4603

Log:
Updating the description of hashed UnIQUE keys



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


Modified: trunk/refman-4.1/storage-engines.xml
===================================================================
--- trunk/refman-4.1/storage-engines.xml	2007-01-23 16:07:49 UTC (rev 4602)
+++ trunk/refman-4.1/storage-engines.xml	2007-01-23 16:11:51 UTC (rev 4603)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 982 bytes

@@ -683,11 +683,11 @@
 
       <listitem>
         <para>
-          A hashed computed index can be used for
-          <literal>UNIQUE</literal>. This allows you to have
-          <literal>UNIQUE</literal> on any combination of columns in a
-          table. (However, you cannot search on a
-          <literal>UNIQUE</literal> computed index.)
+          Optimized compound unique key handling. For compound unique keys
+          (<literal>UNIQUE(col1, col2, ...)</literal>, MyISAM will create
+          a temporary table using a hash of the compound key when the
+          total size of the compound key is too large. The process happens
+          automatically, and cannot be controlled.
         </para>
       </listitem>
 


Modified: trunk/refman-5.0/se-myisam.xml
===================================================================
--- trunk/refman-5.0/se-myisam.xml	2007-01-23 16:07:49 UTC (rev 4602)
+++ trunk/refman-5.0/se-myisam.xml	2007-01-23 16:11:51 UTC (rev 4603)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 936 bytes

@@ -298,11 +298,11 @@
 
     <listitem>
       <para>
-        A hashed computed index can be used for
-        <literal>UNIQUE</literal>. This allows you to have
-        <literal>UNIQUE</literal> on any combination of columns in a
-        table. (However, you cannot search on a
-        <literal>UNIQUE</literal> computed index.)
+        Optimized compound unique key handling. For compound unique keys
+        (<literal>UNIQUE(col1, col2, ...)</literal>, MyISAM will create
+        a temporary table using a hash of the compound key when the
+        total size of the compound key is too large. The process happens
+        automatically, and cannot be controlled.
       </para>
     </listitem>
 


Modified: trunk/refman-5.1/se-myisam.xml
===================================================================
--- trunk/refman-5.1/se-myisam.xml	2007-01-23 16:07:49 UTC (rev 4602)
+++ trunk/refman-5.1/se-myisam.xml	2007-01-23 16:11:51 UTC (rev 4603)
Changed blocks: 3, Lines Added: 7, Lines Deleted: 7; 1377 bytes

@@ -291,11 +291,11 @@
 
     <listitem>
       <para>
-        A hashed computed index can be used for
-        <literal>UNIQUE</literal>. This allows you to have
-        <literal>UNIQUE</literal> on any combination of columns in a
-        table. (However, you cannot search on a
-        <literal>UNIQUE</literal> computed index.)
+        Optimized compound unique key handling. For compound unique keys
+        (<literal>UNIQUE(col1, col2, ...)</literal>, MyISAM will create
+        a temporary table using a hash of the compound key when the
+        total size of the compound key is too large. The process happens
+        automatically, and cannot be controlled.
       </para>
     </listitem>
 

@@ -915,9 +915,10 @@
       </itemizedlist>
 
       <formalpara>
-
         <title>Note</title>
 
+
+
         <para>
           While a compressed table is read-only, and you cannot
           therefore update or add rows in the table, DDL (Data

@@ -925,7 +926,6 @@
           you may still use <literal>DROP</literal> to drop the table,
           and <literal>TRUNCATE</literal> to empty the table.
         </para>
-
       </formalpara>
 
     </section>