History: MariaDB vs MySQL strategy

((MariaDB)) and ((MySQL))'s code bases are diverging. And there is [https://en.wikipedia.org/wiki/Percona_Server_for_MySQL|Percona Server for MySQL].
* https://softwareengineering.stackexchange.com/questions/120178/whats-the-difference-between-mariadb-and-mysql
* https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-features/
* https://mariadb.com/kb/en/mariadb/distributions-which-include-mariadb/
* http://www.zdnet.com/article/shuttleworth-says-ubuntu-is-sticking-with-mysql/
* http://www.zdnet.com/article/oracle-who-fedora-opensuse-will-replace-mysql-with-mariadb/


While the code bases are diverging, it remains manageable. Thus, as of 2023 and for the foreseeable future, we plan to continue to support all 3 equally. Meaning that any issue on should be reported, prioritized and resolved.

Tiki is (like Virtualmin) a component of WikiSuite.org and [https://wikisuite.org/Virtualmin|Virtualmin defaults to MariaDB].

----

I posted about a related issue here (Tiki database was exported from MySQL and imported to MariaDB and this produced some errors): [https://matrix.to/#/!SLEgqpTNTlGYAhzNvK:gitter.im/$PblMCml-uxFXzDGQXkXHWYaMnLfgJnk5ehPp2n-8C34?via=gitter.im&via=matrix.org&via=sans-nuage.fr] {sign user="chibaguy" datetime="2023-03-31T09:53:07+00:00"}