RENAME {DATABASE | SCHEMA} db_name TO new_db_name; is deprecated as of MySQL 5.1.23
Brought to you by:
ansgarbecker
Originally created by: uli.w...@gmail.com
Renaming a database cannot be done with RENAME {DATABASE | SCHEMA} db_name
TO new_db_name; with versions later than 5.1.23 anymore.
For more information see
http://dev.mysql.com/doc/refman/5.1/en/rename-database.html
Best Regards,
Uli
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: uli.w...@gmail.com
Uuuups, that is a bug, sorry....
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: a...@anse.de
Even more, it is explicitely not recommended by the MySQL people, saying "do not use
it even when you have a version which supports it". That feature should be removed.
But I'd say this is an enhancement isn't it? The current solution works, disallowing
it when it's not supported.
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: rosenfie...@gmail.com
The inability to rename a database folder without potentially messing things up is
an issue in MySQL Server.
HeidiSQL performs correctly and allows the user to rename if his/her server supports
it.
Marking this as upstream.
(Although a warning dialog in HeidiSQL pointing to the MySQL documentation would be
a good idea. That's not what's described here though, someone should open a
separate feature request for that.)
Status: Upstream
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: uli.w...@gmail.com
Well took me a while to figure out, why this failed on my server, so either removing
it or showing at least a warning is probably the best idea.