Re: ActiveSupport::Multibyte for better Unicode support

On Sep 29, 2006, at 4:01 , Julian 'Julik' Tarkhanov wrote:

>
>
> On 28-sep-2006, at 4:00, Michael Glaesemann wrote:
>
>> In PostgreSQL, encoding is a database-level setting, not a table
>> attribute. I
> AFAIK it's customizable all the way, from the cluster to the database
> to the tables and columns.
> And the locale of the postmaster user plays it's part too.

Could you please point me to where you can specify table or column  
encodings separate from those of the database? Encoding from the  
client side is negotiated by the client (so you might be sending  
Latin-1 to the server and it gets translated to the database  
encoding) so in some (weak) sense you can handle the data for tables  
and columns in different encodings *on the client side*, but on the  
server side, the encoding is fixed for the database at the time of  
database creation.

At the time of initdb, a default encoding can be chosen for the  
entire cluster, but it can be overridden for individual databases at  
the time of database creation.

http://www.postgresql.org/docs/8.1/interactive/multibyte.html

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
-~----------~----~----~----~------~----~------~--~---