Re:Unicode is, in 2012, still “cutting edge.”
by chadrs on Tuesday July 10, 2012 @05:20PM
(#4226279)
You don't even want to know the hack I had to implement to get non-BMP characters stored in MySQL 5.1 'utf8' column.
[ Parent
| on HN ]
Re:Unicode is, in 2012, still “cutting edge.”
by pjscott on Tuesday July 10, 2012 @06:17PM
(#4226538)
That's exactly why I use the default ISO-8859-1 encoding for all my MySQL tables, try to only stick ASCII into it, and store any Unicode text as binary UTF-8, encoded client-side. It's stupid and shouldn't be necessary, but at least MySQL can't screw it up.