Somebody from the core team? Do you want a patch or sould I keep that in my plugin?
m|a On May 22, 9:03 am, Manfred Stienstra <[EMAIL PROTECTED]> wrote: > > On May 21, 8:47 pm, DHH <[EMAIL PROTECTED]> wrote: > >>> If you use ActiveRecord::Base.connection.create_database you'll > >>> notice > >>> that by default the created db will use latin1 encoding. I created a > >>> plugin to handle different charset and collations (on top of helping > >>> you with other boring DB tasks). > > >> Which database are you talking about specifically? I believe Rails > >> will use whatever the current default is. MySQL, for example, has a > >> installation-wide configuration file that controls that. > > Just a quick note, it's probably best to set the server-wide encoding > to UTF-8. I've seen some instances, mostly with MySQL 4.x where even > with SET NAMES utf8 the MySQL client wouldn't go into UTF-8 mode. > Ending up with mixed charsets in one table is a pita. > > Manfred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
