Change default charset encoding to utf8mb4
for full UTF-8 support
#165
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.
This changeset updates the MySQL client to use
utf8mb4
as the default charset encoding for full UTF-8 support instead of the legacyutf8mb3
charset encoding that was previously used for BC reasons. Theutf8mb4
encoding is available as of MySQL 5.5.3 (released early 2010) and is what most applications would want to use nowadays. For legacy reasons you can still change this to use a different ASCII-compatible charset encoding like this:Builds on top of #135