On Wed, Apr 13, 2011 at 9:57 AM, Tony Primerano <[email protected]>wrote:
> For some reason I didn't start using mysql2 until recently on my > Rails3/1.9.2 project and I just noticed that this change caused some > of my data to display incorrectly. > > I guess the mysql gem doesn't really store data in UTF-8 so I wrote a > migration to fix the broken items. > > My question is, do I need to change anything else in the mysql > configuration since it was created via the mysql gem instead of the > mysql2 gem? > > > These commands show the same information for DBs created via mysql and > mysql2 so I suspect I am safe. :-) > > SHOW VARIABLES LIKE 'collation%'; > SHOW VARIABLES LIKE 'character%'; > > I would set the encoding in my database.yml file just to be safe. encoding: utf8 B. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
