Thanks for the ongoing work here and obviously you've had some successes and learnings along the way. Getting visibility into documentation has a very nice user visible outcome. Serving the needs of the project should be considered part of this. I see user tests of compatibility added, but to strengthen the position of MariaDB within the project CI on their side is needed wherever possible. This makes it a strong position to maintain compatibility with MariaDB throughout there future development. Fixing outstanding compatibility would be a good goal too. e.g. on ponyorm it seems only the CAST as JSON would be a problem (but CI would confirm this) since JSON as alias has been there since 10.2. https://github.com/ponyorm/pony/blob/3f605052edf06cf99eadf70c4959acbc5175682... . With this a quick MariaDB test like https://github.com/PyMySQL/PyMySQL/blob/b4ed6884a1105df0a27f948f52b3e81d5585... (to be MySQLdb compatible) to pass though the expression rather than enclose in a cast is required (get_server_info() is there https://mysqlclient.readthedocs.io/user_guide.html#mysql-c-api-function-mapp... ). As seen with diesel they expect more and a number of database using software are making challenging decisions as to what is supported and require more than just a name but some non-duplicated but easy to maintain code to be able to extend MySQL and MariaDB in the future as they slowly diverge. Other suggestions that need improvement on the CMS front are: * Joomla * PHPBB * SMF * UNA - https://unacms.com On Thu, 11 Apr 2024 at 14:05, Otto Kekäläinen via developers < developers@lists.mariadb.org> wrote:
Hi!
I assume everyone on this mailing list has a GitHub account. Could you please +1 these PRs that add a mention of MariaDB in the documentation of various projects that currently only mention MySQL?
Open each link below and press the thumbs up icon in the lower left corner of the PR description:
https://github.com/bookshelf/bookshelf/pull/2129 https://github.com/ponyorm/pony/pull/708 https://github.com/metabase/metabase/issues/40325 https://github.com/SeaQL/seaql.github.io/pull/116
I am asking this because there are a lot of database tools and libraries out there that work with both MySQL and MariaDB, but they only mention MySQL, which is a pity, because the users of those tools might actually switch from MariaDB to MySQL simply out of confusion/fear that the tool supports only MySQL, which is almost never true.
One of those rare cases is Javascript/Node.js Drizzle ORM which needs changes to support MariaDB. There is already a PR for that, you could +1 it as well: https://github.com/drizzle-team/drizzle-orm/pull/1692
The Rust Diesel ORM has a similar situation going on: https://github.com/diesel-rs/diesel/issues/1882 https://github.com/diesel-rs/diesel/pull/3964
However most projects have absolutely no MySQL-specific things and work with MariaDB, and just needed the docs updated, like was done in these cases:
https://github.com/mysql-net/MySqlConnector/pull/1460 https://github.com/rails/rails/pull/51330 https://github.com/prisma/docs/pull/5706 https://github.com/gregstoll/gallery2/pull/168 https://github.com/coleifer/peewee/pull/2858 _______________________________________________ developers mailing list -- developers@lists.mariadb.org To unsubscribe send an email to developers-leave@lists.mariadb.org