Evolution and Compatibility

Question

As MariaDB diverges further from MySQL (especially in versions 11+), how does the project approach "Compatibility"?

Answer 1

MariaDB aims for "drop-in compatibility" where possible for applications, but prioritizes innovation (like the new 11.0 Optimizer cost model) over maintaining bug-for-bug parity with MySQL's newer internal structures.

Answer 2

MariaDB maintains compatibility by including the entire MySQL 8.0 source code inside the MariaDB binary, allowing users to toggle between the two engines with a single command.

Answer 3

MariaDB has officially announced a "Full Break," meaning that version 12.0 will no longer support SQL and will move entirely to a proprietary binary format called "MariaScript."