DROP [TEMPORARY] TABLE [IF EXISTS] [/*COMMENT TO SAVE*/] tbl_name [, tbl_name] ... [WAIT n|NOWAIT] [RESTRICT | CASCADE]
DROP TABLE removes one or more tables. You must have the
for each table. All table data and the table definition are removed, as well as triggers 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
Important: When a table is dropped, user privileges on the table are not automatically dropped. See GRANT.
If another connection is using the table, a metadata lock is active, and this statement will wait until the lock is released. This is also true for non-transactional tables.
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.
IF EXISTS to prevent an error from occurring for tables that do not
NOTE is generated for each non-existent table when using
IF EXISTS. See SHOW WARNINGS.
If a foreign key references this table, the table cannot be dropped. In this case, it is necessary to drop the foreign key first.
CASCADE are allowed to make porting from other database systems easier. In MariaDB, they do nothing.
It is possible to specify table names as
tab_name. This is useful to delete tables from multiple databases with one statement. See Identifier Qualifiers for details.
The DROP privilege 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.
DROP TABLE automatically commits the current active transaction,
unless you use the
DROP TABLE in replication
DROP TABLE has the following characteristics in replication:
DROP TABLE IF EXISTSare always logged.
IF EXISTSfor tables that don't exist are not written to the binary log.
- Dropping of
TEMPORARYtables are prefixed in the log with
TEMPORARY. These drops are only logged when running statement or mixed mode replication.
DROP TABLEstatement can be logged with up to 3 different
DROP TEMPORARY TABLE list_of_non_transactional_temporary_tables
DROP TEMPORARY TABLE list_of_transactional_temporary_tables
DROP TABLE list_of_normal_tables
Dropping an Internal #sql-... Table
If the mysqld process is killed during an ALTER TABLE you may find a table named #sql-... in your data directory. In MariaDB 10.3, InnoDB tables with this prefix will de deleted automatically during startup. In MariaDB 10.4 we will ensure that 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:
DROP TABLE `#mysql50##sql-...`;
When running an
ALTER TABLE…ALGORITHM=INPLACE that rebuilds the table, InnoDB will create an internal
#sql-ib table. For these tables, the
.frm file will be called something else. In order to drop such a table after a server crash, you must rename the
#sql*.frm file to match the
DROP TABLE Employees, Customers;