MySQL Bugs: #32617: Falcon fails to create table with the same name after unsuccessfull create table

Bug #32617	Falcon fails to create table with the same name after unsuccessfull create table
Submitted:	22 Nov 2007 11:35	Modified:	21 Feb 2008 15:42
Reporter:	Sergey Vojtovich	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Falcon storage engine	Severity:	S3 (Non-critical)
Version:	6.0.4bk	OS:	Linux (FC6)
Assigned to:	Sergey Vojtovich	CPU Architecture:	Any

Description:
After unsuccessful create table statement, it is not possible to create a table with the same name. Drop table fails as well:

CREATE TABLE t1(`a"` INT) ENGINE=Falcon;
ERROR HY000: Can't create table 'test.t1' (errno: 156)
CREATE TABLE t1(a INT) ENGINE=Falcon;
ERROR HY000: Can't create table 'test.t1' (errno: 156)
DROP TABLE t1;
ERROR 42S02: Unknown table 't1'
CREATE TABLE t1(a INT) ENGINE=Falcon;
ERROR HY000: Can't create table 'test.t1' (errno: 156)

Note that with Falcon currently it is not possible to use quotes as field name identifier. It is subject of another bug, thus to create good test case this problem should be triggered differently.

How to repeat:
CREATE TABLE t1(`a"` INT) ENGINE=Falcon;
CREATE TABLE t1(a INT) ENGINE=Falcon;
DROP TABLE t1;
CREATE TABLE t1(a INT) ENGINE=Falcon;

Thank you for the report.

Verified as described.

Bug #33215 was marked as a duplicate to this bug.

Here is a test case which does not rely on invalid table names:

mysql>  create table t5 (f1 integer) Engine=FALCON TABLESPACE nosuchspace;
ERROR 1005 (HY000): Can't create table 'test.t5' (errno: 156)
mysql>  create table t5 (f1 integer) Engine=FALCON;
ERROR 1005 (HY000): Can't create table 'test.t5' (errno: 156)

Sergey, The fix for this is to try to prevent the Falcon metadata and the server metadata from getting out of sync.  Correct propagation of error codes.

This issue can be very frustrating for both support and customers.

Even after the problem which caused the original CREATE is fixed, future CREATEs will keep failing unexplicably (and with the same error message as the first failure).

The problem seem to be fixed - wasn't able to repeat with latest bk sources. Will add a test case to document that it is fixed.

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/41152

ChangeSet@1.2787, 2008-01-23 17:01:26+04:00, svoj@mysql.com +2 -0
  BUG#32617 - Falcon fails to create table with the same name after
              unsuccessfull create table
  
  Added a test case to document that the problem is not repeatable
  anymore.