Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The more MariaDB diverges from MySQL, the more tedious and hacky it gets to support both DBMS with a single driver.
Now that Laravel 11 provides a dedicated database config for MariaDB (#48455), it makes sense to also have a dedicated driver.
Upgrade Guide
The PR is not a breaking change and you can still use MariaDB with the MySQL driver. The ultimate goal, of course, is to remove all MariaDB-specific code from MySQL classes (grammars etc.), but I would only do that in Laravel 12. This gives MariaDB users a year to adjust their config and test the driver. They should switch to the new driver to benefit from MariaDB-specific features, but it doesn't break their application if they miss this change. Ideally, @laravel-shift can recommend it.
TODO
master
branch, theMariaDbConnector
class needs to be adjusted.Plans
#48888 has already collected MariaDB-specific features/improvements we can implement. There are also a few older tickets about differences between MySQL and MariaDB we can revisit.