Bug #8547 Wrong errormessage when dropping table that does not exist in NDB
Submitted: 16 Feb 2005 14:57 Modified: 4 Mar 2005 11:24
Reporter: Magnus Blåudd Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.0 OS:
Assigned to: Magnus Blåudd CPU Architecture:Any

[16 Feb 2005 14:57] Magnus Blåudd
Description:
Wrong error message is returned when user drops a table that does exists as .frm file but does not exists in NDB.

How to repeat:
# Drop a table that does exists as a frm file but not in NDB
drop table t4;
Warnings:
Error	1296	Got error 709 'No such table existed' from NDB

This is not consistent with the error message returned when trying to drop a table that does not exists a s f.rm file.
DROP TABLE t5;
ERROR 42S02: Unknown table 't5'

Suggested fix:
The same error message should be returned in both cases. 

DROP TABLE t4;
ERROR 42S02: Unknown table 't4' "

DROP TABLE t5;
ERROR 42S02: Unknown table 't5' "

DROP TABLE IF EXISTS t5;
Warnings:
Note	1051	Unknown table 't5

DROP TABLE IF EXISTS t4;
Warnings:
Note	1051	Unknown table 't5