MariaDB Foundation’s Post

Doctrine's DBAL made a release 4.3.1 https://lnkd.in/g6cUe4Qg that included a MariaDB fix. This is significant because a nightly test against MariaDB's latest container image discovered that a miscellaneous improvement in the 12.1 preview - https://lnkd.in/gJQHhvDT , Per-table unique FOREIGN KEY constraint names (MDEV-28933), introduced a small compatibility issue. DBAL wasn't quoting foreign key names in the particular 4.3 release series and via a test case of DBAL, discovered this incompatibility. These nightly test cases were created a year ago from information in https://lnkd.in/gDNg7hQ6, where the test failure messaged to our Zulip instance. When messaged I promptly took action to understand what changed. So within a week, there's a fixed version of DBAL for a MariaDB that isn't even released. If the problem happened to be on MariaDB's end we had a chance to fix this before a GA version without any compatibility issues arising. DBAL is just one of many projects using MariaDB's development versions to ensure that our common users are getting the best MariaDB experience with their project. Is the compatibility of your project/infrastructure with MariaDB important enough for you/your users? If so you can message me to see how we can best integrate the CI, potentially even triggered by new versions in our CI. This is made possible with MariaDB Foundation and our sponsors (please make that you!) that keep this and many other community efforts going, so as a user, the experience is bliss.