|From:||Peter Eisentraut <peter_e(at)gmx(dot)net>|
|To:||Martijn van Oosterhout <kleptog(at)svana(dot)org>|
|Cc:||Radek Strnad <radek(dot)strnad(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: WIP patch: Collation support|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Martijn van Oosterhout wrote:
> On Tue, Sep 02, 2008 at 02:50:47PM +0300, Peter Eisentraut wrote:
>> Radek Strnad wrote:
>>> - new collations can be defined with command CREATE COLLATION <collation
>>> name> FOR <character set specification> FROM <existing collation name>
>>> [STRCOLFN <fn name>]
>>> [ <pad characteristic> ] [ <case sensitive> ] [ LCCOLLATE <lc_collate> ]
>>> [ LCCTYPE <lc_ctype> ]
>> How do you plan to make a collation case sensitive or accent sensitive?
>> I have previously commented that this is not a realistic view on how
>> collations work. Since you are apparently planning to use the system
>> locales, I don't see how you can make this work.
> While it's true POSIX locales don't handle this, other collation
> libraries do and we should support them if the user wants.
Do they handle exactly those two attributes specifically? Can you point
out references? Or do you mean, other collation libraries allow their
collations to be configured/customized? I think linguistically it is a
very narrow view of the world to hardcode those two attributes.
|Next Message||Peter Eisentraut||2008-09-02 13:50:01||Re: [PATCH] Cleanup of GUC units code|
|Previous Message||Marko Kreen||2008-09-02 13:45:39||Re: [PATCH] Cleanup of GUC units code|