Author: jstephens
Date: 2007-03-03 07:23:50 +0100 (Sat, 03 Mar 2007)
New Revision: 5158
Log:
Partitioning example used disallowed function in partitioning expression
(Fixes Docs part of Bug #26082)
Modified:
trunk/refman-5.1/partitioning.xml
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2007-03-03 04:48:19 UTC (rev 5157)
+++ trunk/refman-5.1/partitioning.xml 2007-03-03 06:23:50 UTC (rev 5158)
Changed blocks: 2, Lines Added: 3, Lines Deleted: 8; 1379 bytes
@@ -1158,13 +1158,8 @@
Since we cannot use character values in value-lists, we need to
convert these into integers or <literal>NULL</literal>s. For
this purpose, we can use the <literal>ASCII()</literal> function
- on the column value. In addition — due to the use of
- different applications at different times and locations —
- these codes may be either uppercase or lowercase, and the
- <quote>empty</quote> value representing <quote>currently
- unassigned</quote> may actually be a <literal>NULL</literal>, an
- empty string, or a space character. A partitioned table that
- implements this scheme is shown here:
+ on the column value. A partitioned table that implements this
+ scheme is shown here:
</para>
<programlisting>
@@ -1177,7 +1172,7 @@
job_code CHAR(1),
store_id INT
)
-PARTITION BY LIST(ASCII( UCASE(job_code) )) (
+PARTITION BY LIST( ASCII(job_code) ) (
PARTITION management VALUES IN(68, 77, 79, 80),
PARTITION sales VALUES IN(66, 76, 83),
PARTITION technical VALUES IN(65, 69, 71, 73, 84),
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5158 - trunk/refman-5.1 | jon | 3 Mar |