Re: [WIP] collation support revisited (phase 1) - Mailing list pgsql-hackers

From Zdenek Kotala
Subject Re: [WIP] collation support revisited (phase 1)
Date
Msg-id 48860C7D.7030304@sun.com
Whole thread Raw
In response to Re: [WIP] collation support revisited (phase 1)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane napsal(a):
> Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
>> I think if we support UTF8 encoding, than it make sense to create own charsets, 
>> because system locales could have defined collation for that.
> 
> Say what?  I cannot imagine a scenario in which a user-defined encoding
> would be useful. 

I did not mean user defined encoding but user defined charset. For example
cs_CZ.UTF-8@euro locale uses UTF8 encoding and collation is defined on czech 
charset which specifies list of allowed character. If somebody will have 
installed e.g. Turkish locale then he will want to have also Turkish charset in  postgres. I guess, Charset also
defineshow upper/lower case will work (see 
 
i/I in Turkish).

Please, correct me if I wrong.
    thanks Zdenek

-- 
Zdenek Kotala              Sun Microsystems
Prague, Czech Republic     http://sun.com/postgresql



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] GIN improvements
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] GIN improvements