Add unknown collations for MySQL 8 and MariaDB #171
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Jubeki
force-pushed
the
database-collations
branch
from
ec53dbc
to
5cf1cee
Compare
|
Is something blocking this PR or will this only be merged shortly before/after Laravel 11 release? @freekmurze |
|
@freekmurze as Laravel 11 was released yesterday, I think it would be great to have this merged / reviewed. |
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Laravel 11 will change the default collations for MySQL 8 and MariaDB including a new database configuration entry for MariaDB (see laravel/framework#48455)
MySQL 8:
utf8mb4_0900_ai_ci(not supported by MariaDB and MySQL 5.7)MariaDB:
utf8mb4_uca1400_ai_ci(not supported by MySQL 8 and MySQL 5.7)This PR informs Developers of this change so that they can mitigate the issue themself.