Bug #39764 | Datafile already exists error message even after dropping tablespace | ||
---|---|---|---|
Submitted: | 30 Sep 2008 22:42 | Modified: | 9 Oct 2008 21:39 |
Reporter: | Hema Sridharan | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-6.0-backup | OS: | Linux |
Assigned to: | Vladislav Vaintroub | CPU Architecture: | Any |
Tags: | F_TABLESPACE |
[30 Sep 2008 22:42]
Hema Sridharan
[2 Oct 2008 1:01]
Vladislav Vaintroub
Hema, after analyzng it, I believe problem is in test case and Falcon runs ok. doh Notice you test fails for "memory" , i.e just after it ran with "falcon" as default engine. In particular, in case falcon is default engine, "restore" would restore the falcon table t11 and corresponding tablespace file. Subsequent "drop database" will remove the not remove the tablespace file, which is ok IMO (there is no 1-1 correspondence between databases and tablespaces and single tablespace can in theory have tables of different databases). So after the test runs with falcon, "ob" file is left and this should be ok. You'll need to catch it somehow and issue another "drop tablespace" after restore at end of the test In case falcon is _not_ default engine, tablespace clause is simply ignored by create database . "Restore" would restore the table but would not recreate the tablespace file, as backup file has no info about the tablespace (this is what I strongly believe, please this statement with backup guys)
[8 Oct 2008 11:51]
Vladislav Vaintroub
Don't know what to do with it. Hema, do you think it it makes sense to change Category to backup (as you confirmed, the error is in the test case) or close as "No bug"?