From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PG-10 + ICU and abbreviated keys |
Date: | 2017-11-13 20:48:01 |
Message-ID: | VisenaEmail.56.2bbb07f22fccd3a7.15fb720bc0b@tc7-visena |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
På mandag 13. november 2017 kl. 21:40:47, skrev Peter Geoghegan <pg(at)bowt(dot)ie
<mailto:pg(at)bowt(dot)ie>>:
On Mon, Nov 13, 2017 at 11:48 AM, Andreas Joseph Krogh
<andreas(at)visena(dot)com> wrote:
> Ok, so I have to explicitly specify like this:
>
> create table test(id serial primary key, name varchar collate "nb_NO" not
null);
That doesn't look like an ICU locale. You may mean "nb-NO-x-icu". But
otherwise, yes.
Ok, is there a way I can get a list of ICU-collations?
> Will ICU be used here as long as PG is compiled with ICU-suppoert, as the
debian-packages are, or do I have to specify collation-provider?
If you did initdb with a version with ICU support, the ICU collations
should be there.
> Do I have to explicitly specify collation when using ORDER by on that
column for index and abbreviated keys to be used?
Only if you didn't define the column with a per-column collation initially.
Ok, thanks.
Looking forward to this being a per-database setting so it's (hopefully) more
transparent.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Joseph Krogh | 2017-11-13 20:48:54 | Re: PG-10 + ICU and abbreviated keys |
Previous Message | Peter Geoghegan | 2017-11-13 20:46:08 | Re: PG-10 + ICU and abbreviated keys |