Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to v0.12.0 caused special characters to turn to garbage #441

Closed
carbontwelve opened this issue Mar 14, 2021 · 4 comments
Closed

Upgrade to v0.12.0 caused special characters to turn to garbage #441

carbontwelve opened this issue Mar 14, 2021 · 4 comments

Comments

@carbontwelve
Copy link

@carbontwelve carbontwelve commented Mar 14, 2021

Describe the bug

When upgrading to v0.12.0 following the instruction ALTER DATABASE writefreely CHARACTER SET latin1 COLLATE latin1_swedish_ci; caused all emoji and special characters to become corrupted.

For example see the below screen shot, there was an emoji at the end of the post and the pull out to the right was bookended by curly quotes:
image

What I suspect is happened is the altering of the database character set wasn't followed by a conversion of the character set in the database content.

@thebaer
Copy link
Member

@thebaer thebaer commented Apr 7, 2021

It looks like columns on your tables might not have been set correctly... I'd need to check which version this was supposed to happen on. But could you run this query and share the output?

SHOW FULL COLUMNS FROM posts;

We're looking for the content column to have a collation of utf8mb4_bin.

@carbontwelve
Copy link
Author

@carbontwelve carbontwelve commented Apr 15, 2021

The content column is showing as having a collation of utf8mb4_bin.

I have looked at a backup of the database from before migrating and its showing the same. The only thing that seems to have been changed is that the database as a whole has latin1_swedish_ci where as previously it was utf8mb4_general_ci like all my other applications databases.

@thebaer
Copy link
Member

@thebaer thebaer commented Jun 24, 2021

Sorry for the slow response here. I'm really not sure what would cause this, unfortunately, especially if the collation on that column hasn't changed. The best thing to do might be to revert to your previous character set and collation.

@thebaer
Copy link
Member

@thebaer thebaer commented Jun 30, 2021

Since we haven't heard about this affecting anyone else, and it should be fixed from the start with our updated installation instructions, I'm not sure there's anything actionable on this issue, so I'll close it.

@thebaer thebaer closed this Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants