Another possible match MariaDB-(\d+.\d+.\d+) and not needed validation of parth 2 :)

"mariadb-10.9.3" doesn't seem to be a valid MariaDB version.

MariaDB [(none)]> SELECT VERSION();
+---------------------------------------+
| VERSION()                             |
+---------------------------------------+
| 10.9.3-MariaDB-1:10.9.3+maria~ubu2204 |
+---------------------------------------+
1 row in set (0.000 sec)

The valid version passes the test.

@morozov What about this, the official doc:

https://www.doctrine-project.org/projects/doctrine-dbal/en/latest/reference/configuration.html#automatic-platform-version-detection

If you are running a MariaDB database, you should prefix the serverVersion with mariadb- (ex: mariadb-10.2.12).

Everyone using this format (which is suggested in the official doc) is forced to change their serverVersion to 10.9.3-MariaDB for things to work.

"mariadb-10.9.3" doesn't seem to be a valid MariaDB version.

What we need is just a version string x[.x[.x]] for comparison.
We should not care it may or may not actually exists, it's real, or fake.

@morozov After the composer update, I should not research why it does not work anymore. I think a lot of old projects will have the same issue.

MySQL 8 detection also not working well after 68576ab#diff-28b47b91b6b91252a7758495476fc8b338019cccae59cbbd67bd0fe6c87529a5 ... using connection string in symfony like mysql://user:password@host:3306/database?serverVersion=8.0&charset=utf8mb4 worked well before commit, now it requires serverVersion=8.0.0 because version_compare('8.0', '8.0.0', '>=') = FALSE

Everyone who has commented here: Can you please verify that updating DBAL to "~3.5.1@dev" in your composer.json fixes the regression for you?

Everyone who has commented here: Can you please verify that updating DBAL to "~3.5.1@dev" in your composer.json fixes the regression for you?

mariadb-10.9.3 success no any errors anymore