Re: [19] Proposal: function markers to indicate collation/ctype sensitivity - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Date
Msg-id 9B5DB6E2-18D2-4106-84D4-1B0FBD1069E4@justatheory.com
Whole thread Raw
Responses Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
Re: [19] Proposal: function markers to indicate collation/ctype sensitivity
List pgsql-hackers
Hi Jeff,

On Jun 3, 2025, at 23:22, Jeff Davis <pgsql@j-davis.com> wrote:

> If we didn't have separate markers, we'd need to assume that all of
> those objects could be affected by a provider update.

I understand the need to trace these dependencies, but as a function developer with relatively modest understanding of
collationnuances, I’m wondering how I’d know I needed these markers. It seems complicated. Which leads me to think that
adoptionwould be low outside of core. 

Best,

David


Attachment

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Next
From: Fujii Masao
Date:
Subject: Re: Add tab-completion for ALTER TABLE ADD NOT NULL