Re: Pre-proposal: unicode normalized text

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Jeff Davis <pgsql@j-davis.com>, Robert Haas <robertmhaas@gmail.com>, Isaac Morland <isaac.morland@gmail.com>

Cc: Chapman Flack <chap@anastigmatix.net>, Nico Williams <nico@cryptonector.com>, pgsql-hackers@postgresql.org

Date: 2023-10-06T08:10:59Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Try again to fix the MSVC build
- 151ffcf6d8c1 17.0 landed
Additional unicode primitive functions.
- a02b37fc0832 17.0 landed

On 05.10.23 19:30, Jeff Davis wrote:
> Agreed, at least until we understand the set of users per-column
> encoding is important to. I acknowledge that the presence of per-column
> encoding in the standard is some kind of signal there, but not enough
> by itself to justify something so invasive.

The per-column encoding support in SQL is clearly a legacy feature from 
before Unicode.  If one were to write something like SQL today, one 
would most likely just specify, "everything is Unicode".