Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unicode full case mapping: PG_UNICODE_FAST, and standard-compliant UCS_BASIC
Date: 2025-01-18 00:40:07
Message-ID: 580b46bac04894d879b526ccb375a4d548f421e0.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2025-01-17 at 16:06 -0800, Jeff Davis wrote:
> 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().

Forgot to add a link to the discussion. Here are some relevant
messages:

https://www.postgresql.org/message-id/4c9eea58-08a1-4629-a004-439e2cf12de8%40eisentraut.org
https://www.postgresql.org/message-id/610d7f1b-c68c-4eb8-a03d-1515da304c58%40manitou-mail.org

Regards,
Jeff Davis

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-01-18 01:11:41 Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation
Previous Message Jeff Davis 2025-01-18 00:34:43 Re: Add CASEFOLD() function.