Comments on: MySQL Unicode / UTF-8 Support Can Be Dangerous!! http://www.adaruby.com/2006/10/19/mysql-unicode-utf-8-support-can-be-dangerous/?utm_source=rss&utm_medium=rss&utm_campaign=mysql-unicode-utf-8-support-can-be-dangerous Rich Dynamic Applications with Ruby on Rails Fri, 03 Feb 2012 03:32:04 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Hendy Irawan http://www.adaruby.com/2006/10/19/mysql-unicode-utf-8-support-can-be-dangerous/comment-page-1/#comment-58 Hendy Irawan Fri, 03 Nov 2006 01:42:08 +0000 http://adaruby.com/2006/10/19/mysql-unicode-utf-8-support-can-be-dangerous/#comment-58 Yes, I suppose that is correct. The problem is while upgrading, MySQL 5.0 doesn't seem to "label" the old tables correctly. When I say "UTF-8 as default", I'm actually expecting "UTF-8 as default for NEW tables". Existing/old tables should use whatever encoding was used at the time of creation (if it was created with SQL_ASCII encoding as default, I suppose it should be SQL_ASCII from then on). This doesn't seem to be the case in my experience. Yes, I suppose that is correct.

The problem is while upgrading, MySQL 5.0 doesn’t seem to “label” the old tables correctly. When I say “UTF-8 as default”, I’m actually expecting “UTF-8 as default for NEW tables”. Existing/old tables should use whatever encoding was used at the time of creation (if it was created with SQL_ASCII encoding as default, I suppose it should be SQL_ASCII from then on).

This doesn’t seem to be the case in my experience.

]]> By: neo http://www.adaruby.com/2006/10/19/mysql-unicode-utf-8-support-can-be-dangerous/comment-page-1/#comment-57 neo Thu, 02 Nov 2006 19:02:29 +0000 http://adaruby.com/2006/10/19/mysql-unicode-utf-8-support-can-be-dangerous/#comment-57 But, before your mysql upgrade to 5.0 in Step 2, if you had the data in UTF-8, then you shouldn't had this problem, correct ?, But, before your mysql upgrade to 5.0 in Step 2, if you had the data in UTF-8, then
you shouldn’t had this problem, correct ?,

]]>