Skip to content
Discussion options

You must be logged in to vote

Fixed this issue by changing the encoding of the underlying field in the database from utf8mb4_bin to utf8mb4_unicode_ci

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Answer selected by Hannoma
Comment options

You must be logged in to vote
2 replies
@crynobone
Comment options

@johnpuddephatt
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants