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

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part
Date: 2025-10-28 19:51:55
Message-ID: 948630AE-1EF3-42C7-8836-0ED1961DE6F8@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 28, 2025, at 15:38, David E. Wheeler <david(at)justatheory(dot)com> wrote:

> This patch uses existing Postgres functions, of which btrim is one[1].

Accidentally cut out my link before sending!

[1]: https://www.postgresql.org/docs/current/functions-string.html#FUNCTIONS-STRING

D

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2025-10-28 20:03:17 Re: C11: should we use char32_t for unicode code points?
Previous Message Mihail Nikalayeu 2025-10-28 19:44:00 Re: [BUG?] check_exclusion_or_unique_constraint false negative