Re: Jsonpath ** vs lax mode

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Oleg Bartunov <obartunov(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)postgrespro(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Jsonpath ** vs lax mode
Date: 2021-01-20 18:16:34
Message-ID: 20210120181634.GA19308@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2021-Jan-20, Alexander Korotkov wrote:

> My proposal is to make everything after the ** operator use strict mode
> (patch attached). I think this shouldn't be backpatched, just applied to
> the v14. Other suggestions?

I think changing the mode midway through the operation is strange. What
do you think of requiring for ** that mode is strict? That is, if ** is
used and the mode is lax, an error is thrown.


Álvaro Herrera Valdivia, Chile

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2021-01-20 18:25:26 Re: strange error reporting
Previous Message Alexey Kondratov 2021-01-20 18:10:14 Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly