sync uuid creation column with the new upgrade #130
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.
Fix UUID column type for MariaDB compatibility
Problem
When using MariaDB as the database driver for Laravel Translations UI, the migration fails due to an incompatibility with the
uuid
column type. This occurs because MariaDB doesn't natively support theuuid
data type.Error
Running the migration
2024_09_05_100938_create_phrases_table
results in the following error:Solution
Update the migration file to use
char(36)
instead ofuuid()
for MariaDB compatibility. This change aligns with Laravel's recommendation for handling UUIDs in MariaDB as mentioned in the upgrade guide.Changes
In the migration file
create_phrases_table
, replace:with:
Benefits
Testing
Additional Notes
This change is specific to MariaDB compatibility and should not affect the functionality of the package when used with other database systems that support the native
uuid()
method.Closes #[Issue Number]