Bug #29521 Issue CREATE TABLESPACE with same TS name appears to work, but doesn't
Submitted: 3 Jul 2007 13:43 Modified: 31 Oct 2007 6:44
Reporter: Robin Schumacher Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Falcon storage engine Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: Sergey Vojtovich CPU Architecture:Any

[3 Jul 2007 13:43] Robin Schumacher
Description:
Try and create tablespace with same name as existing tablespace results in OK 
message; no error message given

How to repeat:
*** tablespace rmstest2 already exists ***

mysql> create tablespace rmstest2
    -> add datafile 'c:/dev/rmstest22.fts'
    -> engine=falcon;
Query OK, 0 rows affected (0.00 sec)
[3 Jul 2007 17:28] MySQL Verification Team
Thank you for the bug report. The error message is showed in the log error
but not within the mysql client:

c:\dev\6.0>bin\mysql -uroot
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1
Server version: 6.0.1-alpha-nt Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| gimf               |
| mysql              |
+--------------------+
3 rows in set (0.00 sec)

mysql> use gimf;
Database changed
mysql> create tablespace gimfdata1
    -> add datafile 'gimf1.fts'
    -> engine=falcon;
Query OK, 0 rows affected (0.20 sec)

mysql>

c:\dev\6.0>bin\mysqld-nt --standalone --console
070703 14:22:40  InnoDB: Started; log sequence number 0 46409
070703 14:22:41 [Note] Event Scheduler: Loaded 0 events
070703 14:22:41 [Note] bin\mysqld-nt: ready for connections.
Version: '6.0.1-alpha-nt'  socket: ''  port: 3306  Source distribution
Recovering database c:\dev\6.0\data\falcon_master.fts ...
first recovery block is 1
last recovery block is 69
recovery read block is 68
Recovery complete
Exception: tablespace "GIMFDATA1" already exists
[31 Oct 2007 6:44] Sergey Vojtovich
The behaviour has changed since this bug was reported. "CREATE TABLESPACE existing_name" returns error now. See also BUG#31114.