Re: CREATE COLLATION without LOCALE throws error in v15

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Kyle Spearrin <kspearrin(at)bitwarden(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: Justin Baur <jbaur(at)bitwarden(dot)com>, Vince Grassia <vgrassia(at)bitwarden(dot)com>
Subject: Re: CREATE COLLATION without LOCALE throws error in v15
Date: 2022-12-08 19:59:42
Message-ID: f1e8eb753d667afd65a10223ed528077c1421a3c.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 2022-12-08 at 19:29 +0100, Peter Eisentraut wrote:
> The harm is that in the context of database-level collations, the
> analogous syntax means something different.

I see. I certainly agree that we shouldn't document the
lc_ctype=lc_collate hack for CREATE COLLATION for the ICU provider,
because we don't want to encourage it.

Kyle, perhaps after the docs are updated, you can reach out to the
npgsql project to see if they can fix it on their side?

--
Jeff Davis
PostgreSQL Contributor Team - AWS

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kyle Spearrin 2022-12-08 20:02:28 Re: CREATE COLLATION without LOCALE throws error in v15
Previous Message Peter Eisentraut 2022-12-08 18:29:31 Re: CREATE COLLATION without LOCALE throws error in v15