Bug #19625 | CREATE TABLE .... PARTITION BY order not per docs | ||
---|---|---|---|
Submitted: | 8 May 2006 23:22 | Modified: | 12 May 2006 23:33 |
Reporter: | Brian Morin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Partitions | Severity: | S3 (Non-critical) |
Version: | 5.1.9/5.1BK | OS: | Linux (Linux) |
Assigned to: | Jon Stephens | CPU Architecture: | Any |
[8 May 2006 23:22]
Brian Morin
[9 May 2006 0:02]
MySQL Verification Team
Changing Category to Cluster.
[9 May 2006 12:48]
MySQL Verification Team
Thank you for the bug report. mysql> CREATE TABLE `order_bad` ( -> `id` bigint unsigned NOT NULL AUTO_INCREMENT, -> PRIMARY KEY (`id`) -> ) PARTITION BY HASH(id) ENGINE=MyISAM DEFAULT CHARSET=latin1; ERROR 1064 (42000): You have an error in your SQL mysql> CREATE TABLE `order_good` ( -> `id` bigint unsigned NOT NULL AUTO_INCREMENT, -> PRIMARY KEY (`id`) -> ) ENGINE=MyISAM DEFAULT CHARSET=latin1 PARTITION BY HASH(id); Query OK, 0 rows affected (0.02 sec)
[10 May 2006 14:40]
Mikael Ronström
This is a documentation bug. The proper order is [table_options][partition_options]
[12 May 2006 23:33]
Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant product(s). Additional info: Corrected error in CREATE TABLE Syntax. (Note that the examples shown in the Partitioning chapter were correct.)