public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Thom Brown <[email protected]>
To: Jeff Davis <[email protected]>
Cc: Vik Fearing <[email protected]>
Cc: Joe Conway <[email protected]>
Cc: Ian Lawrence Barwick <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Add CASEFOLD() function.
Date: Thu, 19 Jun 2025 16:51:02 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA-aLv7KLoT9yCdiJwRP9PeL_4yNTzQ3T8WJLbTtX=Ld45UOpg@mail.gmail.com>
References: <[email protected]>
	<CAB8KJ=jgnpbDTJS+jOQMzo7b1mPTwM0hCqQBBRgoX_kvyxWVog@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAA-aLv7KLoT9yCdiJwRP9PeL_4yNTzQ3T8WJLbTtX=Ld45UOpg@mail.gmail.com>

On 19.06.25 06:03, Thom Brown wrote:
> Late to the party, but is there an argument for porting this to the 
> citext type? Or supplementing the extension with an additional type 
> ("cftext"? *shrug*). It currently uses lower(), so our current 
> recommendation for dealing with all unicode characters is to use 
> nondeterministic collations.

What is the motivation for wanting a citext variant instead of using 
nondeterministic collations?

view thread (40+ 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], [email protected]
  Subject: Re: Add CASEFOLD() function.
  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