From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | marcin mank <marcin(dot)mank(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Per-column collation |
Date: | 2010-11-16 20:08:16 |
Message-ID: | AANLkTi=M+6wsEAM96g6=bgsD_P=QrO3f0n7TO4iDh88n@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/11/16 marcin mank <marcin(dot)mank(at)gmail(dot)com>:
>> I can only look at the locales that the operating system provides. We
>> could conceivably make some simplifications like stripping off the
>> ".utf8", but then how far do we go and where do we stop? Locale names
>> on Windows look different too. But in general, how do you suppose we
>> should map an operating system locale name to an "acceptable" SQL
>> identifier? You might hope, for example, that we could look through the
>
> It would be nice if we could have some mapping of locale names bult
> in, so one doesn`t have to write alternative sql depending on DB
> server OS:
+1
Pavel
> select * from tab order by foo collate "Polish, Poland"
> select * from tab order by foo collate "pl_PL.UTF-8"
>
> (that`s how it works now, correct?)
>
> Greetings
> Marcin Mańk
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-11-16 20:08:24 | Re: unlogged tables |
Previous Message | Robert Haas | 2010-11-16 20:07:07 | Re: Explain analyze getrusage tracking |