Postgres Pro
Downloads
Home   >   mailing lists

Re: Update Unicode data to Unicode 16.0.0 - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Update Unicode data to Unicode 16.0.0
Date
Msg-id CA+TgmoYKp+CLZhab6fGri3XGhhn5WXs2qVyyo6gFkzP=cRWXjg@mail.gmail.com
Whole thread Raw
In response to Re: Update Unicode data to Unicode 16.0.0  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Update Unicode data to Unicode 16.0.0
List pgsql-hackers
Tree view 
On Tue, Mar 18, 2025 at 2:55 PM Jeff Davis <pgsql@j-davis.com> wrote:
> Continuing on with Unicode 15.1 and accepting the unassigned code point
> *cannot* prevent breakage.

Under your definition, this is true, but I think Jeremy would define
breakage differently. His primary concern, I expect, is *stability*.
Breakage means that the same supposedly-stable results return
different answers on the same data. Under that definition, continuing
under Unicode 15.1 does prevent breakage.

--
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Update Unicode data to Unicode 16.0.0
Next
From: Álvaro Herrera
Date:
Subject: Re: NOT ENFORCED constraint feature