- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 12.1 Data Definition Statements
- 12.1.1 ALTER DATABASE Syntax
- 12.1.2 ALTER LOGFILE GROUP Syntax
- 12.1.3 ALTER SERVER Syntax
- 12.1.4 ALTER TABLE Syntax
- 12.1.5 ALTER TABLESPACE Syntax
- 12.1.6 CREATE DATABASE Syntax
- 12.1.7 CREATE INDEX Syntax
- 12.1.8 CREATE LOGFILE GROUP Syntax
- 12.1.9 CREATE SERVER Syntax
- 12.1.10 CREATE TABLE Syntax
- 12.1.11 CREATE TABLESPACE Syntax
- 12.1.12 DROP DATABASE Syntax
- 12.1.13 DROP INDEX Syntax
- 12.1.14 DROP LOGFILE GROUP Syntax
- 12.1.15 DROP SERVER Syntax
- 12.1.16 DROP TABLE Syntax
- 12.1.17 DROP TABLESPACE Syntax
- 12.1.18 RENAME DATABASE Syntax
- 12.1.19 RENAME TABLE Syntax
RENAME {DATABASE | SCHEMA} db_name TO new_db_name;
This statement was added in MySQL 5.1.7 but was found to be
dangerous and was removed in MySQL 5.1.23. It was intended to
enable upgrading pre-5.1 databases to use the encoding
implemented in 5.1 for mapping database names to database
directory names (see Section 8.2.3, “Mapping of Identifiers to Filenames”).
However, use of this statement could result in loss of database
contents, which is why it was removed. Do not use
RENAME DATABASE in earlier versions in which
it is present.
To perform the task of upgrading database names with the new
encoding, use ALTER DATABASE
instead (see Section 12.1.1, “db_name UPGRADE DATA DIRECTORY
NAMEALTER DATABASE Syntax”).
User Comments
Add your own comment.