Author: jstephens
Date: 2007-11-05 23:41:54 +0100 (Mon, 05 Nov 2007)
New Revision: 8544
Log:
Fixed typo (Thanks, PeterG!)
Modified:
trunk/refman-5.1/partitioning.xml
trunk/refman-6.0/partitioning.xml
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2007-11-05 21:03:32 UTC (rev 8543)
+++ trunk/refman-5.1/partitioning.xml 2007-11-05 22:41:54 UTC (rev 8544)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1103 bytes
@@ -4607,11 +4607,11 @@
<para>
The lone exception to this restriction occurs when
partitioning by [<literal>LINEAR</literal>]
- <literal>KEY</literal> — where it is possible to use
- columns of other types types as partitioning keys —
- because MySQL's internal key-hashing functions produce the
- correct data type from these types. For example, the following
- <literal>CREATE TABLE</literal> statement is valid:
+ <literal>KEY</literal>, where it is possible to use columns of
+ other types as partitioning keys, because MySQL's internal
+ key-hashing functions produce the correct data type from these
+ types. For example, the following <literal>CREATE
+ TABLE</literal> statement is valid:
</para>
<programlisting>
Modified: trunk/refman-6.0/partitioning.xml
===================================================================
--- trunk/refman-6.0/partitioning.xml 2007-11-05 21:03:32 UTC (rev 8543)
+++ trunk/refman-6.0/partitioning.xml 2007-11-05 22:41:54 UTC (rev 8544)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1103 bytes
@@ -4499,11 +4499,11 @@
<para>
The lone exception to this restriction occurs when
partitioning by [<literal>LINEAR</literal>]
- <literal>KEY</literal> — where it is possible to use
- columns of other types types as partitioning keys —
- because MySQL's internal key-hashing functions produce the
- correct data type from these types. For example, the following
- <literal>CREATE TABLE</literal> statement is valid:
+ <literal>KEY</literal>, where it is possible to use columns of
+ other types as partitioning keys, because MySQL's internal
+ key-hashing functions produce the correct data type from these
+ types. For example, the following <literal>CREATE
+ TABLE</literal> statement is valid:
</para>
<programlisting>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8544 - in trunk: refman-5.1 refman-6.0 | jon | 5 Nov |