Bug #16768 DD: DROP LG that does not exist returns wrong error code
Submitted: 25 Jan 2006 3:33 Modified: 7 Feb 2006 5:52
Reporter: Nikolay Grishakin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1 OS:Linux (Linux)
Assigned to: Jonas Oreland CPU Architecture:Any

[25 Jan 2006 3:33] Nikolay Grishakin 
Description:
DROP LOGFILE GGROUP that does not exist returns wrong error code: 1507  "ER_DROP_TABLESPACE_FAILED" instead of ER_DROP_LOGFILEGROUP_FAILED

#lg1 does not exist.
 DROP LOGFILE GROUP lg1
 ENGINE=NDB;

How to repeat:
see above
[26 Jan 2006 1:54] Nikolay Grishakin 
Error message that returned during this failure:
"error returned: failed: 1507: Failed to drop LOGFILE GROUP"
Error message is right, but error code isn't.
[6 Feb 2006 12:22] Jonas Oreland 
I changed error code from ER_{CREATE/ALTER/DROP}_TABLESPACE_FAILED
to ER{CREATE/ALTER/DROP}_FILEGROUP_FAILED
[6 Feb 2006 12:28] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2187
[7 Feb 2006 5:52] Jonas Oreland 
pushed into 5.1.7