Mariadb 11 3 Sql Compat

Rewrite Rules

• Use backticks only when quoting is required. Do not use double quotes for identifiers unless the task explicitly says ANSI_QUOTES is enabled. Do not use square brackets unless the task explicitly says MSSQL mode is enabled.
• Use INSERT ... ON DUPLICATE KEY UPDATE or INSERT IGNORE for upsert-style flows. Do not emit PostgreSQL ON CONFLICT.
• Use UPDATE table_references SET ... with joins in the table_references section. Do not emit PostgreSQL UPDATE ... FROM.
• Use WITH ... SELECT for CTE reads. Do not emit WITH ... UPDATE or WITH ... DELETE; those are newer than MariaDB 11.3.
• Do not alias single-table DELETE FROM tbl AS t ...; that form is only documented from MariaDB 11.6. Rewrite to unaliased single-table delete or multi-table delete syntax.
• For identity columns, prefer AUTO_INCREMENT or SERIAL; do not assume PostgreSQL GENERATED ... AS IDENTITY.
• Treat JSON as MariaDB's alias type, not MySQL's binary JSON implementation.
• Quote or rename reserved words instead of assuming another dialect's escaping rules.
• If project instructions are stricter than MariaDB 11.3, follow the project instructions.

Checker

The checker lives at scripts/check_mariadb_11_3_sql_compat.py.

It currently flags high-signal patterns that regularly leak in from other dialects:

• ON CONFLICT
• top-level UPDATE ... FROM
• top-level WITH ... UPDATE
• top-level WITH ... DELETE
• single-table DELETE FROM ... AS alias
• PostgreSQL casts with ::type
• PostgreSQL identity syntax
• bracket-quoted identifiers

The checker does not prove correctness. If the SQL is generated dynamically, validate the final rendered SQL, not just the template fragment.

Source Map

Read references/mariadb-11-3-compatibility.md when you need:

• statement syntax or version gates
• quoting rules or reserved words
• data type behavior for JSON, UUID, AUTO_INCREMENT, or SERIAL
• documented MariaDB alternatives for foreign-dialect syntax

Output Expectations

• In reviews, identify the incompatible fragment, explain why it is not valid for MariaDB 11.3, and provide the MariaDB form to use instead.
• In implementations, emit MariaDB 11.3 SQL directly instead of showing multiple dialects unless the user asks for a comparison.
• If compatibility depends on SQL_MODE and the task does not specify it, assume MariaDB 11.3 with the default sql_mode documented by MariaDB.