GitHub account owners - please +1 these MariaDB mention PRs
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
Thanks, Otto, this is a great beginning! I also see that a second part of the list is already merged by the projects. Good! On Thu, 11 Apr 2024 at 06: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
-- Yours truly, Nikita Malyavin
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
Hi all! Here is a new one I filed today: https://github.com/charles-001/dolphie/pull/60 Please +1 it :)
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
Otto, Well done on getting it merged. Dolphie requires grants https://github.com/charles-001/dolphie?tab=readme-ov-file#mysql-grants-requi... that don't correspond to what MariaDB needs (10.5+) and its replication monitoring implementation isn't MariaDB compatible (well maybe non-gtid mode is). Seems to detect galera on wsrep_on existing (https://github.com/charles-001/dolphie/blob/4d12c604716bf9f180cfb0c8c7a0d21e...) which might hide some replication things. Its InnoDB monitoring capability also may start to have incompatibilities with MariaDB as I know several IS tables were removed (some replaced, not sure how completely). Looking at all queries: https://github.com/charles-001/dolphie/blob/main/dolphie/Modules/Queries.py ANY_VALUE is used (https://jira.mariadb.org/browse/MDEV-10426) and it also depends on performance_schema and sys schema. On the face of it, it doesn't look like it's going to take long for a MariaDB user to hit any of these incompatibilities and then which community person is going to fix it? Spelling fixes was a good bundling to favour merging. Nice wording on persuading too. On Fri, 26 Apr 2024 at 13:20, Otto Kekäläinen via developers <developers@lists.mariadb.org> wrote:
Hi all!
Here is a new one I filed today: https://github.com/charles-001/dolphie/pull/60
Please +1 it :)
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
Hi! While putting MariaDB 11.4 in Debian I came across more software that has official docs or modules for MySQL backends, but no mention of MariaDB - even though in reality in every Debian release in the past 8 years those modules have been running exclusively MariaDB. Perhaps somebody in the MariaDB Foundation can follow up with these and see if the respective upstreams have appetite to rename modules to something-mariadb instead of something-mysql, or at least document prominently the fact that MariaDB is indeed supported? For example PowerDNS has a MySQL module (https://github.com/PowerDNS/pdns/tree/master/modules) but neither the module nor the docs (https://doc.powerdns.com/authoritative/backends/generic-mysql.html) mention anything about MariaDB support. However in Debian the package (https://packages.debian.org/unstable/pdns-backend-mysql) depends on the default-mysql-server which in turn has been pointing to MariaDB in Debian since 2016. On Wed, 10 Apr 2024 at 21:04, Otto Kekäläinen <otto@kekalainen.net> 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
participants (3)
-
Daniel Black -
Nikita Malyavin -
Otto Kekäläinen