Fix: Set charset and collation to utf8mb4_general_ci to avoid unknown collation error #41
Conversation
This file contains hidden or 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
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.
Problem
When executing the SQL query, I encountered the following error:
This typically happens when the MySQL server version is older and doesn't support the 'utf8mb4_0900_ai_ci' collation (which was introduced in MySQL 8.0).
Solution
To ensure broader compatibility, I updated the database configuration to explicitly use:
charset:utf8mb4collation:utf8mb4_general_ciThis collation is widely supported across MySQL versions and still provides good Unicode support.
Notes
Tested the connection and confirmed the error no longer occurs.