This repository has been archived by the owner on Sep 27, 2024. It is now read-only.
Add utf8 charset explicitly to table definitions #150
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.
For any databases that do not have utf8 as the default. Without this
setting the tables are created with the default, but are treated as
utf8, which can result in errors:
ERROR 1366 (HY000): Incorrect string value: '\xE2\x84\xAF\x0A -...' for column 'response_body' at row 1
This came up in the context of a legacy MySQL application.
The kind of project where this project is exceedingly useful!
Before submitting, please review the contributor guidelines. In particular:
bin/appraisal rspec
to verify.bin/rake lint
to verify.