Re: Define jsonpath functions as stable

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Chapman Flack <chap(at)anastigmatix(dot)net>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Define jsonpath functions as stable
Date: 2019-07-29 22:27:56
Message-ID: CAPpHfdvfwDV73kWAkJjzBfUmu89q1oFTnEP-s2BMHL4_wzKdmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jul 29, 2019 at 5:55 PM Chapman Flack <chap(at)anastigmatix(dot)net> wrote:
> On 7/29/19 10:25 AM, Alexander Korotkov wrote:
>
> > * like_regex predicate uses our regular expression engine, which
> > deviates from standard.
>
> I still favor adding some element to the syntax (like a 'posix' or 'pg'
> keyword in the grammar for like_regex) that identifies it as using
> a different regexp flavor, so the way forward to a possible compliant
> version later is not needlessly blocked (or consigned to a
> standard_conforming_strings-like experience).

What do you think about renaming existing operator from like_regex to
pg_like_regex? Or introducing special flag indicating that PostgreSQL
regex engine is used ('p' for instance)?

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-07-29 23:35:20 Re: POC: Cleaning up orphaned files using undo logs
Previous Message Joe Conway 2019-07-29 22:27:31 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)