Re: ActiveSupport::Multibyte for better Unicode support

On Sep 28, 2006, at 9:15 , Pete Yandell wrote:

> We can certainly make sure tables created with migrations have the
> right character set, and we can at least check and give a warning if
> the various character sets (database, table, connection, Rails) don't
> match up.
>
> I don't know what's required for Postgres, but I'll build for MySQL
> and somebody with Postgres experience can extend from there.

In PostgreSQL, encoding is a database-level setting, not a table  
attribute. IIRC, changing from one encoding to another requires  
dumping the database, passing the dump through iconv, creating a new  
database with the target encoding, and loading the dump into the new  
database.

Michael Glaesemann
grzm seespotcode net



--~--~---------~--~----~------------~-------~--~----~
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@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to 
rubyonrails-core-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---