Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part - Mailing list pgsql-hackers

From jian he
Subject Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Date
Msg-id CACJufxGAmcwq33nr_MmgnGdGo7E10c55kCA22DQ4n9FBUOZmTA@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
List pgsql-hackers
On Wed, Oct 29, 2025 at 3:39 AM David E. Wheeler <david@justatheory.com> wrote:
>

> Updated patches attached.
>
> Best,
>
> David
>
hi.

/*
 * All node's type of jsonpath expression
 *
 * These become part of the on-disk representation of the jsonpath type.
 * Therefore, to preserve pg_upgradability, the order must not be changed, and
 * new values must be added at the end.
 *
 * It is recommended that switch cases etc. in other parts of the code also
 * use this order, to maintain some consistency.
 */
typedef enum JsonPathItemType

some "switch" in the attached patch does not preserve the JsonPathItemType order
consistency, like executeItemOptUnwrapTarget.


--
jian
https://www.enterprisedb.com/



pgsql-hackers by date:

Previous
From: Michael Banck
Date:
Subject: Re: How can end users know the cause of LR slot sync delays?
Next
From: Jim Jones
Date:
Subject: Re: [PoC] XMLCast (SQL/XML X025)