Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC
Date
Msg-id f9562cf9871805bb4d4bb6675bbd43aabee4f12a.camel@j-davis.com
Whole thread Raw
In response to Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC
List pgsql-hackers
On Wed, 2025-01-15 at 13:21 -0800, Jeff Davis wrote:
> I plan to commit 0001 and 0002 soon.

Committed 0001 and 0002.

Upon reviewing the discussion threads, I removed the Unicode "adjust to
Cased" behavior when titlecasing. As Peter pointed out[1], it doesn't
match the documentation or expectations for INITCAP().

I also expanded the C tests a lot in 0001 so that it compares
exhaustively against ICU for single-codepoint strings, and also added
more multi-codepoint test strings.

I don't plan to commit 0003 in v18, so I'm considering this series to
be done for now. We can revisit whether UCS_BASIC should change
behavior in 19.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Re: Fwd: Re: proposal: schema variables
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Add roman support for to_number function