[11.x] Add mariadb to databases config

[Jubeki]

This adds proper support for MariaDB, as the default/recommended collation for mysql and mariadb has changed.

See laravel/laravel#6239
See laravel/laravel#6240
See laravel/laravel#6241

Changes:

• Splits of the MariaDB Database Configuration.
• Changes default collation for MySQL to utf8mb4_0900_ai_ci
• Changes default collation for MariaDB to utf8mb4_uca1400_ai_ci
• Test MariaDB Configuration against MariaDB database.

Changes to the config still needs to be applied to Testbench.

[Jubeki]

Any ideas why the MariaDB 10 tests fail? I can't find a location were I missed adding mariadb as an available connection.

[taylorotwell]

Why change this?

[driesvints]

@taylorotwell these are the mariadb tests and previously it used the mysql connection. Now it uses its dedicated mariadb connection which this PR creates.

[Jubeki]

So that the MariaDB Database tests are run against the MariaDB configuration instead of the MySQL configuration. Because of the changed collation in the mysql configuration which does not exist in MariaDB, this would throw an error.

[crynobone]

This should be expected since Testbench holds it's own configuration files.

[Jubeki]

This should be expected since Testbench holds it's own configuration files.

I forget about Testbench. Thanks!

[Tristan-MyAnaPro]

Hi @Jubeki / @driesvints

Now that we'll have a dedicated config for MariaDB, shouldn't the default collation for MariaDB be uca1400_ai_ci ?

uca1400_ai_ci is based on Unicode 14 and available in MariaDB since 10.10.1 (Laravel 11.x will support
MariaDB 10.11+ so we're covered https://laravel.com/docs/master/database).

Note that I used uca1400_ai_ci and not utf8mb4_uca1400_ai_ci as this collation can be used with any of these charset utf8mb3, utf8mb4, ucs2, utf16, utf32 (although I don't really understand why you'd want to use a less than 4 bytes charset (utf8mb3) with this collation 🤔)

What do you think about it ?

[Jubeki]

@Tristan-MyAnaPro this seems like a good idea.
Seems like there are already plans to make uca1400_ai_ci the default. See https://jira.mariadb.org/browse/MDEV-30164

Probably as of MariaDB 11.4. See https://jira.mariadb.org/browse/MDEV-19123

[driesvints]

@Jubeki are you still working on this one?

[Jubeki]

@driesvints in my opinion I am finished with this PR. I only rebase against slim-skeleton-11.x sometimes.

One point for discussion open is only:

• Change default charset for mariadb to uca1400_ai_ci in the config without waiting for MariaDB to make the change. (Which I would be in favour of)

(Taylor put the PR into Draft, so I left it like that)

[grooverdan]

Note - MDEV-32336 deb default config - use collation-server = utf8mb4_uca1400_ai_ci MariaDB/server#2775 for 11.3

That without an explicit collation utf8mb4 uses the collation uca1400_ai_ci. Applying this to Debian/Ubuntu will flow through to the mariadb:11.3 container on the next release.

If you want to ensure that the next version of MariaDB (server and container) to be released is going to be Laravel compatible (and give you a chance to tell MariaDB to fix things before release :-) ) you can use the following container images:

• quay.io/mariadb-foundation/mariadb-devel:very-latest (beta/rc)
• quay.io/mariadb-foundation/mariadb-devel:latest (stable)
• quay.io/mariadb-foundation/mariadb-devel:latest-lts (stable and long term maintained)
• quay.io/mariadb-foundation/mariadb-devel:ealiest-lts (old and still maintained)

These are the latest version of completed code merged into the main branches - https://quay.io/repository/mariadb-foundation/mariadb-devel?tab=tags . The code there has passed review and is expected to work so this isn't a beta tree, just an unreleased version.

information:

• https://mariadb.org/new-service-quay-io-mariadb-foundation-mariadb-devel/ (service)
• https://mariadb.org/mariadb-server-docker-official-images-healthcheck-without-mysqladmin/ (healthcheck)

Or just ask me. Happy to help.

[driesvints]

@Jubeki we might want to resend in this PR as Taylor probably force-pushed his commits.

[Jubeki]

@grooverdan Thanks for the information about the changes in MariaDB. I applied the default collation in the config accordingly. I don't think the newer container image is needed here, because the tested mariadb version already supports the new collation, but of course the Laravel Team can decide to test against the new image. (FYI Laravel 11 will probably be released in February 2024 as far as I know).

@driesvints I rebased against slim-skeleton-11.x. Should I mark this PR as Ready for Review?

[driesvints]

@Jubeki yeah go for it