From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Pre-proposal: unicode normalized text |
Date: | 2024-03-14 18:07:00 |
Message-ID: | fb51f027ef2d06841103c6ce509c9c4aa6d561d3.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 2024-02-29 at 17:02 -0800, Jeff Davis wrote:
> Attached is an implementation of a per-database option STRICT_UNICODE
> which enforces the use of assigned code points only.
The CF app doesn't seem to point at the latest patch:
https://www.postgresql.org/message-id/a0e85aca6e03042881924c4b31a840a915a9d349.camel@j-davis.com
which is perhaps why nobody has looked at it yet.
But in any case, I'm OK if this gets bumped to 18. I still think it's a
good feature, but some of the value will come later in v18 anyway, when
I plan to propose support for case folding. Case folding is a version
of lowercasing with compatibility guarantees when you only use assigned
code points.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Melanie Plageman | 2024-03-14 18:16:25 | Re: BitmapHeapScan streaming read user and prelim refactoring |
Previous Message | Andrey M. Borodin | 2024-03-14 18:06:04 | Re: UUID v7 |