Re: Should URI::mysql Switch to DBD::MariaDB?

Looks like the Oracle folks are having a bit of a time keeping up with the devs that jumped ship.

"...main image supports Postgres, SQLite, and MySQL..."

Looks like only one of those is being maintained by a big corporation.

"...Perhaps we need to add a MariaDB variant with a separate Docker tag..."

Or maybe the other way around...make MariaDB the new core option and force people to use a special image for MySql?

Celebrate Intellectual Diversity

Comment on Re: Should URI::mysql Switch to DBD::MariaDB?

Replies are listed 'Best First'.
Re^2: Should URI::mysql Switch to DBD::MariaDB? by Theory (Beadle) on Jan 03, 2025 at 16:50 UTC
“Looks like only one of those is being maintained by a big corporation.” I suppose the functionality would be pretty much the same by depending on MariaDB stuff. One could still connect to MySQL. For the Homebrew formula, though, I don't see a client-only Homebrew formula for MariaDB, alas. I see only the full package and a c connector, but maybe that includes the client library and CLI? “Or maybe the other way around...make MariaDB the new core option and force people to use a special image for MySql?” I'd be wary of breaking things unexpectedly for users.	[reply]

Replies are listed 'Best First'.

Re^2: Should URI::mysql Switch to DBD::MariaDB?
by Theory (Beadle) on Jan 03, 2025 at 16:50 UTC

“Looks like only one of those is being maintained by a big corporation.”

I suppose the functionality would be pretty much the same by depending on MariaDB stuff. One could still connect to MySQL. For the Homebrew formula, though, I don't see a client-only Homebrew formula for MariaDB, alas. I see only the full package and a c connector, but maybe that includes the client library and CLI?

“Or maybe the other way around...make MariaDB the new core option and force people to use a special image for MySql?”

I'd be wary of breaking things unexpectedly for users.

[reply]