| From: | marcin mank <marcin(dot)mank(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Per-column collation |
| Date: | 2010-11-16 20:05:16 |
| Message-ID: | AANLkTi=D1t4cJhmPXNGyWUUKKsK6U9gJFMTDCr_GE1ah@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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:
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:07:07 | Re: Explain analyze getrusage tracking |
| Previous Message | Pavel Stehule | 2010-11-16 19:59:50 | Re: Per-column collation |