5 ms·
And software developers, don't forget to implement the 4 byte characters too please. Utter nightmare dealing with MySQL. I believe 4 byte characters still even
by belluchan 13y ago
And software developers, don't forget to implement the 4 byte characters too please. Utter nightmare dealing with MySQL. I believe 4 byte characters still even break github comments.
- 90minuteAPI 13y agoAbout 2 weeks I tried to file a bug with our backend guys about 4-byte characters wreaking havoc on our API. My example broke the bug tracker's (bugzilla) comment system as well. I chuckled.
- jeltz 13y agoI assume Bugzilla broke due to being backed by MySQL. Bugzilla itself is written in Perl so should have no problem.
- lmm 13y agoAt my last job I checked in a test case for our astral character handling. And broke the build server.
- MBCook 13y agoYeah. We've noticed, to our own amusement, that Jira (we're on an older version) can't handle non-ASCII. Makes entering tickets involving other languages fun.
- ggreer 13y agoI ran into that issue with MySQL's utf-8 handling. It was 𝒜wesome: http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are-𝒜wesome/ http://geoff.greer.fm/2012/08/12/character-encoding-bugs-are...
- guard-of-terra 13y agoMySQL was a Norwegian company at the beginning, but you won't believe. It's one of the worst products when it comes to I18N and especially to Unicode. They still kind of store unicode text as a chain of encoded utf8 characters, if I'm not wrong. Their stupid command line utility still defaults to LATIN1 for input and output despite my locale clearly saying .UTF-8. People in their IRC channel still refuse to admit anything of this as a problem.
- jeltz 13y agoThe horrible unicode support in MySQL fits well with its general careless attitude toward data integrity. Minor correction: MySQL was Swedish and InnoDB Finnish.