What problem does it solve? Generated SQL often assumes standard DROP TABLE semantics, but MariaDB diverges in ways that cause errors or data loss: RESTRICT/CASCADE are no-ops, multi-table drops are partial, DDL implicitly commits, and DROP TABLE fails on views or FK-referenced tables. This Skill captures those deltas so DROP TABLE statements targeting MariaDB are correct the first time. ## Core Features & Use Cases - MariaDB behavior deltas: Covers RESTRICT/CASCADE being parsed but inert, partial drops in multi-table statements, IF EXISTS note-level warnings, and automatic trigger removal. - Safety guards: Documents DROP TEMPORARY TABLE to avoid dropping a same-named base table, foreign-key blocking (ER_ROW_IS_REFERENCED) with the foreign_key_checks workaround, and WAIT/NOWAIT lock-wait bounds. - Correct alternatives: Points to DROP VIEW for views, CREATE OR REPLACE TABLE for atomic replacement, and TRUNCATE TABLE vs DELETE FROM for emptying a table. - Use Case: When asked to write a migration script that drops and recreates a table in MariaDB 11.8, produce CREATE OR REPLACE TABLE instead of a non-atomic DROP plus CREATE pair. ## Quick Start Ask the AI to write or review a MariaDB DROP TABLE statement, for example dropping several tables safely while tolerating missing ones and bounding the metadata-lock wait.
