Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Date: 2024-09-25 21:03:57
Message-ID: 145894.1727298237@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Florents Tselai <florents(dot)tselai(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florents Tselai 2024-09-25 22:28:16 Re: Docs pg_restore: Shouldn't there be a note about -n ?
Previous Message Alvaro Herrera 2024-09-25 20:14:53 Re: not null constraints, again