public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Jeff Davis <[email protected]>
To: Daniel Verite <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: Jeremy Schneider <[email protected]>
Cc: [email protected]
Subject: Re: Built-in CTYPE provider
Date: Thu, 4 Apr 2024 14:05:27 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 01.04.24 21:52, Jeff Davis wrote:
> On Tue, 2024-03-26 at 08:04 +0100, Peter Eisentraut wrote:
>> The patch set v27 is ok with me, modulo (a) discussion about initcap
>> semantics, and (b) what collation to assign to ucs_basic, which can
>> be
>> revisited later.
> 
> Attached v28.
> 
> The remaining patches are for full case mapping and PG_UNICODE_FAST.
> 
> I am fine waiting until July to get these remaining patches committed.
> That would give us time to sort out details like:
> 
> * Get consensus that it's OK to change UCS_BASIC.
> * Figure out if we need a pg-specific locale and whether
> PG_UNICODE_FAST is the right name.
> * Make sure that full case mapping interacts with regexes in a sane way
> (probably it needs to just fall back to simple case mapping, but
> perhaps that's worth a discussion).
> * Implement case folding.
> * Implement a more unicode-friendly TITLECASE() function, which could
> offer a number of options that don't fit well with INITCAP().
> * Figure out if UPPER()/LOWER() should also have some of those options.
> 
> Thoughts?

Yeah, I think it's good to give some more time to work out these things. 
  The features committed for PG17 so far are solid, so it's a good point 
to pause.

view thread (39+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Built-in CTYPE provider
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox