Re: More jsonpath methods: translate, split, join

From: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: More jsonpath methods: translate, split, join
Date: 2026-06-19 07:19:11
Message-ID: CA+v5N41NR976cjSugjpOem6MZLcgOquY0+ZvvHiacmz7nBWFPg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2026 at 10:53 PM Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
wrote:

> On Mon, Apr 13, 2026 at 5:57 AM Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
> wrote:
>
>> Hello hackers,
>>
>> This is a follow-up to the work recently merged in bd4f879.
>> In hindsight, I regret not pushing these through for the previous cycle,
>> as they represent the "missing pieces" for users trying to perform data
>> cleaning entirely within the JSONPath engine.
>> With these we can significantly reduce the need for users to "drop out"
>> of JSONPath
>> into standard SQL for basic string-to-string-or-array-and-back workflows.
>>
>>
> Seems this one got overlooked, so I took a look. The first patch applies,
> but the second needs a rebase.
>

Thanks for having a look Corey,

here's a consolidated v2 .

Attachment Content-Type Size
v2-0001-Add-more-jsonpath-string-methods-.translate-.spli.patch application/octet-stream 37.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2026-06-19 07:22:28 Re: Unexpected behavior after OOM errors
Previous Message Matthias van de Meent 2026-06-19 07:18:03 Re: Unexpected behavior after OOM errors