MySQL: Specify UTF-8 charset for versions table #681
Merged
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.
Fixes #651
This change configures MySQL to use UTF-8 for the
versions
table.Even modern versions of MySQL still use
latin1
as the default characterencoding. (https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html)
Many users are not aware of this, and run into trouble when they try to use
PaperTrail in apps that otherwise tend to use UTF-8. Postgres, by
comparison, uses UTF-8 except in the unusual case where the OS is configured
with a custom locale (http://www.postgresql.org/docs/9.4/static/multibyte.html).