Bug #22182 | Renaming database doesn't work | ||
---|---|---|---|
Submitted: | 9 Sep 2006 10:38 | Modified: | 15 Jun 2007 8:30 |
Reporter: | Georg Richter | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 5.2 | OS: | Any (all) |
Assigned to: | CPU Architecture: | Any |
[9 Sep 2006 10:38]
Georg Richter
[18 Sep 2006 0:18]
MySQL Verification Team
Thank you for the bug report. miguel@hegel:~/dbs/5.1f> bin/mysql -uroot Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 4 to server version: 5.1.12-beta-debug Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> create database falcon1; Query OK, 1 row affected (0.00 sec) mysql> use falcon1; Database changed mysql> create table t (s1 int) engine=falcon; Query OK, 0 rows affected (0.12 sec) mysql> rename database falcon1 to falcon2; Query OK, 0 rows affected (0.01 sec) mysql> insert into t values (0); ERROR 1030 (HY000): Got error 157 from storage engine mysql>
[14 Jun 2007 15:33]
Jim Starkey
This works nicely with the new Falcon table space scheme.
[14 Jun 2007 20:32]
Hakan Küçükyılmaz
falcon_bug_22182.test passes now Test(s) which will be run though they are marked as disabled: falcon_bug_22182 : Bug#22182 2006-08-24 hakank (Get pushbuild green) TEST RESULT TIME (ms) ------------------------------------------------------- falcon_bug_22182 [ pass ] 307 -------------------------------------------------------
[15 Jun 2007 8:30]
MC Brown
A note has been added to the 6.0.1 changelog.