From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Allow tailoring of ICU locales with custom rules |
Date: | 2023-03-08 20:57:29 |
Message-ID: | 36a6e89689716c2ca1fae8adc8e84601a041121c.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Wed, 2023-03-08 at 16:03 +0000, Peter Eisentraut wrote:
> Allow tailoring of ICU locales with custom rules
Late review:
* Should throw error when provider != icu and rules != NULL
* Explain what the example means. By itself, users might get confused
wondering why someone would want to do that.
* Also consider a more practical example?
* It appears rules IS NULL behaves differently from rules=''. Is that
desired? For instance:
create collation c1(provider=icu,
locale='und-u-ka-shifted-ks-level1',
deterministic=false);
create collation c2(provider=icu,
locale='und-u-ka-shifted-ks-level1',
rules='',
deterministic=false);
select 'a b' collate c1 = 'ab' collate c1; -- true
select 'a b' collate c2 = 'ab' collate c2; -- false
* Can you document the interaction between locale keywords
("@colStrength=primary") and a rule like '[strength 2]'?
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2023-03-08 22:13:00 | Re: pgsql: 001_libpq_pipeline.pl: use Test::Differences if available |
Previous Message | Daniel Gustafsson | 2023-03-08 19:20:54 | Re: lz4 --rm on Ubuntu 18.04 (Add LZ4 compression to pg_dump) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2023-03-08 21:10:25 | Re: proposal - get_extension_version function |
Previous Message | Regina Obe | 2023-03-08 20:18:06 | RE: [PATCH] Support % wildcard in extension upgrade filenames |