Bug #33212 | DROP TABLESPACE does not fail on non-existing Falcon tablespace | ||
---|---|---|---|
Submitted: | 13 Dec 2007 13:35 | Modified: | 16 Mar 2008 11:20 |
Reporter: | Philip Stoev | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.4 | OS: | Any |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
Tags: | Falcon tablespace |
[13 Dec 2007 13:35]
Philip Stoev
[13 Dec 2007 16:24]
Kevin Lewis
Sergey, Please look at this when you get a chance. It is another Falcon Tablespace issue. I think that users should be able to redirect the location of temporary tables just like regular tables.
[16 Dec 2007 6:25]
MySQL Verification Team
Thank you for the bug report. Verified on main and team tree: [miguel@amanhecer 6.0f]$ bin/mysql -uroot test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 6.0.5-alpha-debug Source distribution Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> drop tablespace nosuchspace engine = 'Falcon'; Query OK, 0 rows affected (0.47 sec) mysql>
[22 Jan 2008 17:15]
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/41102 ChangeSet@1.2778, 2008-01-22 21:00:29+04:00, svoj@mysql.com +8 -0 BUG#33212 - DROP TABLESPACE does not fail on non-existing Falcon tablespace Dropping non-existing Falcon tablespace silently succeeds, whereas it should return error.
[12 Mar 2008 23:02]
Bugs System
Pushed into 6.0.4-alpha
[16 Mar 2008 11:20]
MC Brown
A note has been added to the 6.0.4 changelog: Dropping a tablespace for the Falcon storage engine when the specified tablespace does not exist would silently succeed, instead of generating a suitable error message.