Bug #22155 Double rename failure
Submitted: 9 Sep 2006 5:48 Modified: 6 Sep 2007 10:22
Reporter: Georg Richter Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version:5.2 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[9 Sep 2006 5:48] Georg Richter
Description:
If I rename a Falcon table, then rename it again, I get an error message.
If I rename a MyISAM table, then rename it again, I get no error message.

How to repeat:
mysql> create database jstar18;
Query OK, 1 row affected (0.00 sec)

mysql> create database jstar19;
Query OK, 1 row affected (0.00 sec)

mysql> use jstar18;
Database changed
mysql> create table t1 (s1 int) engine = myisam;
Query OK, 0 rows affected (0.00 sec)

mysql> rename table t1 to jstar19.t1;
Query OK, 0 rows affected (0.00 sec)

mysql> rename table jstar19.t1 to t1;
Query OK, 0 rows affected (0.00 sec)

mysql> create table t2 (s1 int) engine = jstar;
Query OK, 0 rows affected (0.11 sec)

mysql> rename table t2 to jstar19.t2;
Query OK, 0 rows affected (0.00 sec)

mysql> rename table jstar19.t2 to t2;
ERROR 1025 (HY000): Error on rename of './jstar19/t2' to './jstar18/t2' (errno: 157)
[12 Sep 2006 16:15] Hakan Küçükyılmaz
See test case falcon_bug_161.test for reproduction.
[25 Jan 2007 21:15] Ann Harrison
Renaming tables across databases doesn't work.  The initial rename
didn't produce an error, but it didn't produce a table either.  The
second rename failed because there was no table to rename.
[20 Apr 2007 9:38] Hakan Küçükyılmaz
Test case renamed to falcon_bug_22155.test to reflect correct bug number.
[30 Aug 2007 17:31] Kevin Lewis
This seems to be fixed.  George, can you verify?
[4 Sep 2007 18:25] Peter Gulutzan
I don't think Georg needs to re-check; the original reporter was me.
(Georg copied the bugs that I reported from mantis to bugs.mysql.com.)

I have re-tested with a few variations, I confirm that the
bug has disappeared.
[4 Sep 2007 18:55] Kevin Lewis
Fixed in 6.0.2-alpha
[6 Sep 2007 10:22] MC Brown
A note has been added to the 6.0.2 changelog: 

Renaming tables to or from Falcon tablespaces would raise an error