RENAME TABLE [IF EXISTS] tbl_name [WAIT n | NOWAIT] TO new_tbl_name [, tbl_name2 TO new_tbl_name2] ...
This statement renames one or more tables or views, but not the privileges associated with them.
MariaDB starting with 10.5.2
If this directive is used, one will not get an error if the table to be renamed doesn't exist.
The rename operation is done atomically, which means that no other session can
access any of the tables while the rename is running. For example, if you have
an existing table
old_table, you can create another table
new_table that has the same structure but is empty, and then
replace the existing table with the empty one as follows (assuming that
backup_table does not already exist):
CREATE TABLE new_table (...); RENAME TABLE old_table TO backup_table, new_table TO old_table;
tbl_name can optionally be specified as
tbl_name. See Identifier Qualifiers. This allows to use
RENAME to move a table from a database to another (as long as they are on the same filesystem):
RENAME TABLE db1.t TO db2.t;
Note that moving a table to another database is not possible if it has some triggers. Trying to do so produces the following error:
ERROR 1435 (HY000): Trigger in wrong schema
Also, views cannot be moved to another database:
ERROR 1450 (HY000): Changing schema from 'old_db' to 'new_db' is not allowed.
RENAME TABLE renames more than one table and one renaming fails, all renames executed by the same statement are rolled back.
Renames are always executed in the specified order. Knowing this, it is also possible to swap two tables' names:
RENAME TABLE t1 TO tmp_table, t2 TO t1, tmp_table TO t2;
Atomic RENAME TABLE
MariaDB starting with 10.6.0
From MariaDB 10.6,
RENAME TABLE is atomic for most engines, including InnoDB, MyRocks, MyISAM and Aria (MDEV-23842).
This means that if there is a crash (server down or power outage) during
RENAME TABLE, all tables will revert to their original names and any changes to trigger files will be reverted.
In older MariaDB version there was a small chance that, during a server crash happening in the middle of
RENAME TABLE, some tables could have been renamed (in the worst case partly) while others would not be renamed.
See MDEV-17567 "Atomic DDL" for more information.