Bug #37668 | No error message if tables are created in Falcon tablespaces with special names | ||
---|---|---|---|
Submitted: | 26 Jun 2008 13:59 | Modified: | 9 Jan 2009 13:54 |
Reporter: | John Embretsen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.5, 6.0 bzr | OS: | Any |
Assigned to: | Sergey Vojtovich | CPU Architecture: | Any |
Tags: | F_TABLESPACE, falcon |
[26 Jun 2008 13:59]
John Embretsen
[26 Jun 2008 19:08]
Sveta Smirnova
Thank you for the report. Verified as described.
[2 Sep 2008 14:48]
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/53071 2806 Sergey Vojtovich 2008-09-02 BUG#37668 - No error message if tables are created in Falcon tablespaces with special names Creating Falcon tablespace with 'FALCON_MASTER' name was silently accepted. As 'FALCON_MASTER' is the name of falcon internal tablespace it must be rejected. With this fix an error is returned if user attempts to create tablespace with 'FALCON_MASTER' name.
[30 Sep 2008 9:59]
Sergey Vojtovich
Was pushed to 6.0.8 Sep 20.
[9 Jan 2009 13:54]
MC Brown
A note was added to the 6.0.8 changelog: It was possible to create a tasblespace using the name of one of the Falcon system tablespaces, FALCON_MASTER, FALCON_TEMPORARY, or FALCON_BACKLOG without an error message being raised. A suitable error is now produced when an attempt is made to create a table with the same name as a Falcon system tablespace.