Skip to content

Latest commit

 

History

History
75 lines (50 loc) · 2.47 KB

sql-statement-create-database.md

File metadata and controls

75 lines (50 loc) · 2.47 KB
title summary aliases
CREATE DATABASE | TiDB SQL Statement Reference
An overview of the usage of CREATE DATABASE for the TiDB database.
/docs/stable/sql-statements/sql-statement-create-database/
/docs/v4.0/sql-statements/sql-statement-create-database/
/docs/stable/reference/sql/statements/create-database/
/docs/v4.0/reference/sql/statements/create-database/

CREATE DATABASE

This statement creates a new database in TiDB. The MySQL terminology for 'database' most closely maps to a schema in the SQL standard.

Synopsis

CreateDatabaseStmt:

CreateDatabaseStmt

IfNotExists:

IfNotExists

DBName:

DBName

DatabaseOptionListOpt:

DatabaseOptionListOpt

Syntax

The CREATE DATABASE statement is used to create a database, and to specify the default properties of the database, such as the default character set and collation. CREATE SCHEMA is a synonym for CREATE DATABASE.

CREATE {DATABASE | SCHEMA} [IF NOT EXISTS] db_name
    [create_specification] ...

create_specification:
    [DEFAULT] CHARACTER SET [=] charset_name
  | [DEFAULT] COLLATE [=] collation_name

If you create an existing database and does not specify IF NOT EXISTS, an error is displayed.

The create_specification option is used to specify the specific CHARACTER SET and COLLATE in the database. Currently, TiDB only supports some of the character sets and collations. For details, see Character Set and Collation Support.

Examples

mysql> CREATE DATABASE mynewdatabase;
Query OK, 0 rows affected (0.09 sec)

mysql> USE mynewdatabase;
Database changed
mysql> CREATE TABLE t1 (a int);
Query OK, 0 rows affected (0.11 sec)

mysql> SHOW TABLES;
+-------------------------+
| Tables_in_mynewdatabase |
+-------------------------+
| t1                      |
+-------------------------+
1 row in set (0.00 sec)

MySQL compatibility

This statement is understood to be fully compatible with MySQL. Any compatibility differences should be reported via an issue on GitHub.

See also