What problem does it solve? Writing CREATE TRIGGER statements for MariaDB often fails because standard SQL trigger assumptions do not hold: there is no ALTER TRIGGER, SQL SECURITY is invalid, and version-specific features like multi-event triggers only exist in MariaDB 12.0+. This Skill provides the exact MariaDB delta so generated or reviewed trigger code is syntactically and semantically correct. ## Core Features & Use Cases - MariaDB-specific grammar reference: Covers OR REPLACE, DEFINER, IF NOT EXISTS, FOLLOWS/PRECEDES trigger ordering, and multi-event triggers with INSERTING/UPDATING/DELETING predicates (since 12.0). - Common LLM trap table: Maps frequent mistakes (ALTER TRIGGER, NEW.col in DELETE triggers, COMMIT in trigger bodies, SQL SECURITY) to the correct MariaDB form. - Restriction and firing-behavior rules: Documents OLD/NEW row-reference rules, ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG, and how REPLACE, INSERT ... ON DUPLICATE KEY UPDATE, and LOAD DATA fire triggers. - Use Case: When asked to write an audit trigger that logs INSERT, UPDATE, and DELETE on a table, produce a single multi-event trigger for MariaDB 12.0+ or three correctly ordered per-event triggers for current LTS versions. ## Quick Start Ask the AI to write a MariaDB trigger that clamps a column value before update on a given table, and it will apply the correct MariaDB syntax and restrictions.
