read mysql text column (utf8 charset) as string column #660
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.
Encountered with the same problem as #464 and #510 , where
text
type columns in mysql are interpreted as binary ones naively, which is technically ok, according to the mysql doc that thetext
types are basically justblob
types, except for additional charset requirements.But it's quite an inconvenient for users must do decoding themselves on the final result. So I made and tested this patch in our environment as an easy workaround. Note that we only use UTF8 charset for
text
fields in our databases, so this patch only works for UTF8 text fields. For other encodings like GBK, SHIFT_JIS, BIG5, etc., it won't work, additional decoding is still needed.If anyone interested, I recommend checking out this crate
encoding_rs
, then doing decoding steps according to the mysql field charset info.