MySQL Bugs: #12114: Wrong node group in partition leads to table name not reusable in MySQL Cluster

Bug #12114	Wrong node group in partition leads to table name not reusable in MySQL Cluster
Submitted:	22 Jul 2005 14:38	Modified:	1 Aug 2005 16:45
Reporter:	Mikael Ronström	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S3 (Non-critical)
Version:	5.1.0	OS:	Linux (RHEL)
Assigned to:	Mikael Ronström	CPU Architecture:	Any

Description:
CREATE TABLE t1 (a int)
PARTITION BY RANGE (a)
(PARTITION p1 VALUES LESS THAN (10) NODEGROUP 12);
will fail
after that
CREATE TABLE t1 (a int)
PARTITION BY RANGE (a)
(PARTITION p1 VALUES LESS THAN (10));
will also fail since previous erratic CREATE TABLE didn't clean up properly

How to repeat:
See description

Suggested fix:
Write proper error handling in execCREATE_TABLE_REQ when CREATE_FRAGMENTATION_REQ
fails

Wrong NODEGROUP in CREATE TABLE with partitioning and MySQL Cluster
leads to table name locked after failed CREATE TABLE

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 5.1.1 changelog per conversation with Mikael.