| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow tailoring of ICU locales with custom rules |
| Date: | 2023-03-08 06:06:48 |
| Message-ID: | d9d003d2a4630c9000177d7c7c348cb84cbc9992.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2023-03-03 at 13:45 +0100, Peter Eisentraut wrote:
> You can mess with people by setting up your databases like this:
>
> initdb -D data --locale-provider=icu --icu-rules='&a < c < b < e < d'
>
> ;-)
Would we be the first major database to support custom collation rules?
This sounds useful for testing, experimentation, hacking, etc.
What are some of the use cases? Is it helpful to comply with unusual or
outdated standards or formats? Maybe there are people using special
delimiters/terminators and they need them to be treated a certain way
during comparisons?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-03-08 06:19:33 | Re: Normalization of utility queries in pg_stat_statements |
| Previous Message | Jeff Davis | 2023-03-08 05:55:07 | Re: Move defaults toward ICU in 16? |