A simpler way to deal with two byte characters.
I can’t say enough about Redmine. Rivit uses it to Manage Projects, Help Desk Issues, and Time and Attendance. I’ll speak more to how we use it in a future Blog. But I wanted to focus on an ongoing issue we’ve had and how we dealt with it.
Our implementation of Redmine uses MYSQL. It’s cloud-based. When we initially set this up years ago, we didn’t notice that new databases were created with UTF8_swedish_ci collation and character set. Redmine worked great. But…. as we started allowing international clients into Redmine they started to complain about an Error 500 showing up. They couldn’t save any issues that they reported to us. We triaged the problem and found out it was double-byte characters. Japanese, accented characters, etc… could not be entered into a subject, description or comment.
We finally found out that it was the MySQL table definition that was causing the problem. Most people who reported this issue attempted to use the SQL “ALTER table” command to change the collation and the field level characters set. This has the potential issue of losing data.
ALTER DATABASE <database_name> CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
ALTER TABLE mytable CONVERT TO CHARACTER SET utf8mb4
Success. No Data loss. Redmine now has the ability to use double-byte characters.
Rivit Technology Partners Inc. The leading Application Archiving Tool, Dcom is celebrating Ten years! Wow… it’s been 10 years since Rivit introduced its first Notes application