All pages
Powered by GitBook
1 of 1

Loading...

DROP TABLE

Delete one or more tables. This command removes the table definitions and all stored data permanently, and can also delete temporary tables.

Syntax

Description

DROP TABLE removes one or more tables. You must have the DROP privilege for each table. All table data and the table definition are removed, as well as associated to the table, so be careful with this statement! If any of the tables named in the argument list do not exist, MariaDB returns an error indicating by name which non-existing tables it was unable to drop, but it also drops all of the tables in the list that do exist.

Important: When a table is dropped, user privileges on the table are not automatically dropped. See .

If another thread is using the table in an explicit transaction or an autocommit transaction, then the thread acquires a on the table. The DROP TABLE statement will wait in the "Waiting for table metadata lock" until the MDL is released. MDLs are released in the following cases:

  • If an MDL is acquired in an explicit transaction, then the MDL will be released when the transaction ends.

  • If an MDL is acquired in an autocommit transaction, then the MDL will be released when the statement ends.

  • Transactional and non-transactional tables are handled the same.

Note that for a partitioned table, DROP TABLE permanently removes the table definition, all of its partitions, and all of the data which was stored in those partitions. It also removes the partitioning definition (.par) file associated with the dropped table.

For each referenced table, DROP TABLE drops a temporary table with that name, if it exists. If it does not exist, and the TEMPORARY keyword is not used, it drops a non-temporary table with the same name, if it exists. The TEMPORARY keyword ensures that a non-temporary table will not accidentally be dropped.

Use IF EXISTS to prevent an error from occurring for tables that do not exist. A NOTE is generated for each non-existent table when usingIF EXISTS. See .

If a references this table, the table cannot be dropped. In this case, it is necessary to drop the foreign key first.

RESTRICT and CASCADE are allowed to make porting from other database systems easier. In MariaDB, they do nothing.

The comment before the table names (/*COMMENT TO SAVE*/) is stored in the . That feature can be used by replication tools to send their internal messages.

It is possible to specify table names as db_name.tab_name. This is useful to delete tables from multiple databases with one statement. See for details.

The is required to use DROP TABLE on non-temporary tables. For temporary tables, no privilege is required, because such tables are only visible for the current session.

Note: DROP TABLE automatically commits the current active transaction, unless you use the TEMPORARY keyword.

DROP TABLE reliably deletes table remnants inside a storage engine even if the .frm file is missing.

DROP TABLE does not reliably delete table remnants inside a storage engine even if the .frm file is missing. A missing .frm file will result in the statement failing.

WAIT/NOWAIT

Set the lock wait timeout. See .

DROP TABLE in replication

DROP TABLE has the following characteristics in :

  • DROP TABLE IF EXISTS are always logged.

  • DROP TABLE without IF EXISTS for tables that don't exist are not written to the .

  • Dropping of TEMPORARY tables are prefixed in the log with TEMPORARY. These drops are only logged when running

DROP TABLE on the primary is treated on the replica as DROP TABLE IF EXISTS. You can change that by setting to STRICT.

Dropping an Internal #sql-... Table

if the is killed during an , you may find a table named #sql-... in your data directory. These temporary tables will always be deleted automatically.

If you want to delete one of these tables explicitly you can do so by using the following syntax:

When running an ALTER TABLE…ALGORITHM=INPLACE that rebuilds the table, InnoDB will create an internal #sql-ib table.

The same name as the .frm file is used for the intermediate copy of the table. The #sql-ib names are used by TRUNCATE and delayed DROP.

The #sql-ib tables will be deleted automatically.

Dropping All Tables in a Database

The best way to drop all tables in a database is by executing , which will drop the database itself, and all tables in it.

However, if you want to drop all tables in the database, but you also want to keep the database itself and any other non-table objects in it, then you would need to execute DROP TABLE to drop each individual table. You can construct these DROP TABLE commands by querying the table in the database. For example:

Atomic DROP TABLE

MariaDB starting with

DROP TABLE for a single table is atomic () for most engines, including InnoDB, MyRocks, MyISAM and Aria. This means that if there is a crash (server down or power outage) during DROP TABLE, all tables that have been processed so far will be completely dropped, including related trigger files and status entries, and the will include a DROP TABLE statement for the dropped tables. Tables for which the drop had not started will be left intact.DROP TABLE was extended to be able to delete a table that was only partly dropped (), as explained above. Atomic DROP TABLE is the final piece to make DROP TABLE fully reliable. Dropping multiple tables is crash-safe. See for more information.

There is a small chance that, during a server crash happening in the middle of DROP TABLE, some storage engines that were using multiple storage files, like

Examples

Notes

Beware that DROP TABLE can drop both tables and . This is mainly done to allow old tools like (previously mysqldump) to work with sequences.

See Also

This page is licensed: GPLv2, originally from

DROP [TEMPORARY] TABLE [IF EXISTS] [/*COMMENT TO SAVE*/]
    tbl_name [, tbl_name] ...
    [WAIT n|NOWAIT]
    [RESTRICT | CASCADE]
or
replication.
  • One DROP TABLE statement can be logged with up to 3 different DROP statements:

    • DROP TEMPORARY TABLE list_of_non_transactional_temporary_tables

    • DROP TEMPORARY TABLE list_of_transactional_temporary_tables

    • DROP TABLE list_of_normal_tables

  • , could have only a part of its internal files dropped. In
    , DROP TABLE was extended to be able to delete a table that was only partly dropped (
    ) as explained above. Atomic DROP TABLE is the final piece to make DROP TABLE fully reliable. Dropping multiple tables is crash-safe. See
    for more information.
    Variable slave-ddl-exec-mode.
    triggers
    GRANT
    metadata lock (MDL)
    thread state
    SHOW WARNINGS
    foreign key
    binary log
    Identifier Qualifiers
    DROP privilege
    WAIT and NOWAIT
    replication
    binary log
    slave-ddl-exec-mode
    DROP TABLE is atomic.
    mariadbd process
    ALTER TABLE
    DROP DATABASE
    TABLES
    information_schema
    10.6.1
    MDEV-25180
    binary log
    MDEV-11412
    Atomic DDL
    sequences
    mariadb-dump
    CREATE TABLE
    ALTER TABLE
    SHOW CREATE TABLE
    DROP SEQUENCE
    fill_help_tables.sql
    statement
    mixed mode
    MyISAM
    MDEV-11412
    Atomic DDL
    DROP TABLE `#mysql50##sql-...`;
    SELECT CONCAT('DROP TABLE IF EXISTS `', TABLE_SCHEMA, '`.`', TABLE_NAME, '`;')
    FROM information_schema.TABLES
    WHERE TABLE_SCHEMA = 'mydb';
    DROP TABLE Employees, Customers;
    MariaDB 10.5