From: jon
Date: September 2 2006 5:34am
Subject: svn commit - mysqldoc@docsrva: r3204 - trunk/refman-5.1
List-Archive: http://lists.mysql.com/commits/11302
Message-Id: <200609020534.k825YMeF002692@docsrva.mysql.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Author: jstephens
Date: 2006-09-02 07:34:16 +0200 (Sat, 02 Sep 2006)
New Revision: 3204
Log:
Documenting Partitioning bugfixes:
Bug #15890, Bug #20548, Bug #21143,
Bug #21173, Bug #21357, Bug #21339,
Bug #21350, Bug #21658, Bug #21862
Modified:
trunk/refman-5.1/news-5.1.xml
trunk/refman-5.1/partitioning.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-5.1/news-5.1.xml
===================================================================
--- trunk/refman-5.1/news-5.1.xml 2006-09-02 03:16:22 UTC (rev 3203)
+++ trunk/refman-5.1/news-5.1.xml 2006-09-02 05:34:16 UTC (rev 3204)
Changed blocks: 3, Lines Added: 106, Lines Deleted: 2; 4676 bytes
@@ -628,6 +628,110 @@
REPAIR TABLE tbl_name QUICK;
+
+
+
+ The server's handling of the number of partitions or
+ subpartitions specified in a PARTITIONS
+ or SUBPARTITIONS clause was changed.
+ Beginning with this release, the number of partitions must:
+
+
+
+
+
+ be a positive, non-zero integer
+
+
+
+
+
+ not have any leading zeroes
+
+
+
+
+
+ not be an expression
+
+
+
+
+
+ Also beginning with this version, no attempt is made to
+ convert, truncate, or evaluate a PARTITIONS
+ or SUBPARTITIONS value; instead, the
+ CREATE TABLE or ALTER
+ TABLE statement containing the
+ PARTITIONS or
+ SUBPARTITIONS clause now fails with an
+ appropriate error message. (Bug #15890)
+
+
+
+
+
+
+ A misleading error message was displayed when attempting to
+ define a unique key that was not valid for a partitioned
+ table. (Bug #21862)
+
+
+
+
+
+ Errors could be generated during the execution of certain
+ prepared statements that ran queries on partitioned tables.
+ (Bug #21658)
+
+
+
+
+
+ Using relative paths for DATA DIRECTORY or
+ INDEX DIRECTORY with a partitioned table
+ generated a warning rather than an error, and caused
+ junk files to be created in the server's data
+ directory. (Bug #21350)
+
+
+
+
+
+ Using EXPLAIN PARTITIONS with a query on a
+ table whose partitioning expression was based on the value of
+ a DATE column could sometimes cause the
+ server to crash. (Bug #21339)
+
+
+
+
+
+ Running SHOW TABLE STATUS on any
+ InnoDB table having at least one record
+ could crash the server. Note that this was not due to any
+ issue in the InnoDB storage engine, but
+ rather with AUTO_INCREMENT handling in the
+ partitioning code — however, the table did not have to
+ have an AUTO_INCREMENT column for the bug
+ to manifest. (Bug #21173)
+
+
+
+
+
+ Some ALTER TABLE statements affecting a
+ table's subpartitioning could hang. (Bug #21143)
+
+
+
+
+
+ Scheduled events that invoked stored procedures executing DDL
+ operations on partitioned tables could crash the server. (Bug
+ #20548)
+
+
@@ -651,7 +755,7 @@
The server used #sql as a prefix for hidden
- table names, but it is also possible for users to use that as
+ table names, but it was also possible for users to use that as
a table name prefix, which caused some operations to fail. Now
the server uses #.sql as the prefix. (Bug
#1405)
@@ -1626,7 +1730,7 @@
subpartitions, could sometimes crash the server. These issues
were associated with a failure reported in the
partition_range test. (Bug #20766, Bug
- #20767, Bug #20893)
+ #20767, Bug #20893, Bug #21357)
Modified: trunk/refman-5.1/partitioning.xml
===================================================================
--- trunk/refman-5.1/partitioning.xml 2006-09-02 03:16:22 UTC (rev 3203)
+++ trunk/refman-5.1/partitioning.xml 2006-09-02 05:34:16 UTC (rev 3204)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 904 bytes
@@ -666,6 +666,16 @@
partition names mypart and
MyPart.
+
+
+ When you specify the number of partitions for the table, this must
+ be expressed as a positive, non-zero integer literal with no
+ leading zeroes, and may not be an expression such as
+ 0.8E+01 or 6-2, even if it
+ evaluates as an integer. (Beginning with MySQL 5.1.12, decimal
+ fractions are no longer truncated, but instead are disallowed
+ entirely.)
+
In the sections that follow, we do not necessarily provide all
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-09-02 03:16:22 UTC (rev 3203)
+++ trunk/refman-5.1/sql-syntax.xml 2006-09-02 05:34:16 UTC (rev 3204)
Changed blocks: 2, Lines Added: 38, Lines Deleted: 1; 2079 bytes
@@ -895,7 +895,10 @@
primary key) that the table might have, and the column or
columns used in the partitioning expression, as discussed in
Partitioning
- Limitations: Partitioning Keys and Unique Keys.
+ Limitations: Partitioning Keys and Unique Keys. The
+ CREATE TABLE ... PARTITION BY rules for specifying the
+ number of partitions also apply to ALTER
+ TABLE ... PARTITION BY.
@@ -3529,6 +3532,40 @@
integer value.
+
+
+
+ MySQL 5.1.12 introduces rigourous checking of the value used
+ in a PARTITIONS or
+ SUBPARTITIONS clause. Beginning with this
+ version, this value must adhere to the following rules:
+
+
+
+
+
+ The value must be a positive, non-zero integer.
+
+
+
+
+
+ No leading zeroes are permitted.
+
+
+
+
+
+ The value must be an integer literal, and cannot not be an
+ expression. For example, PARTITIONS
+ 0.2E+01 is not allowed, even though
+ 0.2E+01 evaluates to
+ 2. (Bug #15890)
+
+
+
+
+