MySQL & MariaDB
Planned. The danger model is mapped: online DDL ALGORITHM traps, implicit commits, charset rewrites, replication-unsafe statements, destructive partition operations.
A MySQL corpus exists behind --engine=mysql over a real MySQL grammar. It is not offered on any plan yet and not held to the Postgres evidence bar. The danger model is mapped, ALGORITHM=INPLACE versus COPY traps in online DDL, the implicit commit every DDL statement carries, charset and collation changes that rewrite a table, replication-unsafe statements, destructive partition operations, and live-schema context is not available for it.
Planned means the corpus ships when its fixtures run both directions against a real MySQL matrix. Tell us if you need it sooner.
What gets built next bends toward what connected teams actually need, tell us.
Also in Databases
- PostgreSQL 13–17
- SQLitebeta
- SurrealDBbeta