What problem does it solve? Writing correct RENAME TABLE statements for MariaDB is error-prone because its behavior differs from other databases: it is fully atomic across multiple pairs, refuses to run inside transactions or under LOCK TABLES, requires a specific four-privilege set, and blocks cross-database moves for views and tables with triggers. This Skill gives AI agents the exact MariaDB-specific rules so generated or reviewed SQL avoids these pitfalls. ## Core Features & Use Cases - Atomic multi-table renames: Explains left-to-right execution with full rollback on any failure, enabling the classic one-statement table-swap pattern. - Restriction and privilege reference: Covers the ER_LOCK_OR_ACTIVE_TRANSACTION restriction, the ALTER+DROP / CREATE+INSERT privilege split, and cross-database move blocks for views and trigger-bearing tables. - Syntax details: Documents IF EXISTS, WAIT/NOWAIT lock-wait control, TEMPORARY table support, and the TABLE/TABLES interchangeability. - Use Case: When asked to swap a rebuilt table into production, the agent emits RENAME TABLE old_table TO backup_table, new_table TO old_table; as one atomic statement instead of unsafe multi-statement DROP/rename juggling. ## Quick Start Ask the agent to write or review a MariaDB RENAME TABLE statement, such as swapping two tables atomically or moving a table to another database.
