Comments on: UTF-8 and MySQL http://candrews.integralblue.com/2009/01/utf-8-and-mysql/ Please excuse the ugliness of this site. Just remember, as McCoy said to Kirk so many times, "D*&@!$ Jim! I'm an engineer, not a web designer!" Mon, 10 Oct 2011 22:00:40 +0000 hourly 1 http://wordpress.org/?v= By: Ian Mackinnon http://candrews.integralblue.com/2009/01/utf-8-and-mysql/comment-page-1/#comment-88 Ian Mackinnon Thu, 26 Aug 2010 15:33:15 +0000 http://candrews.integralblue.com/?p=23#comment-88 Thanks, this is really helpful! One note - "default-character-set" needs to be preceded by two dashes though in your post this seems to have been converted to a hyphen so I can't be copied and pasted. Thanks, this is really helpful!

One note – “default-character-set” needs to be preceded by two dashes though in your post this seems to have been converted to a hyphen so I can’t be copied and pasted.

]]> By: miqrogroove http://candrews.integralblue.com/2009/01/utf-8-and-mysql/comment-page-1/#comment-63 miqrogroove Sun, 20 Dec 2009 20:57:31 +0000 http://candrews.integralblue.com/?p=23#comment-63 > I checked the documentation for MySQL Connector/J (the JDBC driver), and it says that the connection is UTF-8 I just surfed in and noticed your DB problem here. Actually, your MySQL Connector encoding was the original cause. If you had ensured the text in the scripts was UTF-8 and forced the connection to match the single-byte (latin1) encoding of the DB table, then you would have had a binary-safe storage layer. What threw you off track here was changing the table encoding to UTF-8. As soon as you did that, it became necessary to guarantee everything between the script and the table was UTF-8 as well, to prevent implicit latin1-to-UTF8 conversion. (That conversion is bad for binary data) On the bright side, now all of your string columns will use chars instead of bytes :P > I checked the documentation for MySQL Connector/J (the JDBC driver), and it says that the connection is UTF-8

I just surfed in and noticed your DB problem here. Actually, your MySQL Connector encoding was the original cause. If you had ensured the text in the scripts was UTF-8 and forced the connection to match the single-byte (latin1) encoding of the DB table, then you would have had a binary-safe storage layer.

What threw you off track here was changing the table encoding to UTF-8. As soon as you did that, it became necessary to guarantee everything between the script and the table was UTF-8 as well, to prevent implicit latin1-to-UTF8 conversion. (That conversion is bad for binary data)

On the bright side, now all of your string columns will use chars instead of bytes :P ]]>