Add support for MariaDB #144
Open
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.
Problem
Currently MariaDB is not supported.
MariaDB’s grammar is very similar to MySQL’s, both should use the same
binary(%d)column type.Additionally, the
typeEfficientUuidmethod determines the column type based on the grammar class name rather than its parent type. This causes issues when using a custom grammar class because developers must name it exactly the same as the parent class forlaravel-model-uuidto work correctly.laravel-model-uuid/src/LaravelModelUuidServiceProvider.php
Lines 28 to 35 in 2132680
Solution
The solution is to check the parent type of the grammar class instead of relying on its name.
This makes the logic more flexible and ensures compatibility with MariaDB and any future MySQL or PostgreSQL variations.