From: Tom Lane <tgl@sss.pgh.pa.us>
To: Florents Tselai <florents.tselai@gmail.com>
cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
In-reply-to: <CA+v5N40sJF39m0v7h=QN86zGp0CUf9F1WKasnZy9nNVj_VhCZQ@mail.gmail.com>
References: <CA+v5N40sJF39m0v7h=QN86zGp0CUf9F1WKasnZy9nNVj_VhCZQ@mail.gmail.com>
Comments: In-reply-to Florents Tselai <florents.tselai@gmail.com>
	message dated "Wed, 25 Sep 2024 21:17:20 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <145893.1727298237.1@sss.pgh.pa.us>
Date: Wed, 25 Sep 2024 17:03:57 -0400
Message-ID: <145894.1727298237@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/145894.1727298237%40sss.pgh.pa.us>
Precedence: bulk

Florents Tselai <florents.tselai@gmail.com> writes:
> This patch is a follow-up and generalization to [0].
> It adds the following jsonpath methods:  lower, upper, initcap, l/r/btrim,
> replace, split_part.

How are you going to deal with the fact that this makes jsonpath
operations not guaranteed immutable?  (See commit cb599b9dd
for some context.)  Those are all going to have behavior that's
dependent on the underlying locale.

We have the kluge of having separate "_tz" functions to support
non-immutable datetime operations, but that way doesn't seem like
it's going to scale well to multiple sources of mutability.

			regards, tom lane