Re: SQL/JSON path issues/questions

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL/JSON path issues/questions
Date: 2019-06-28 05:09:53
Message-ID: 20190628050953.GA26234@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-Jun-28, Alexander Korotkov wrote:

> On Tue, Jun 25, 2019 at 6:38 PM Liudmila Mantrova
> <l(dot)mantrova(at)postgrespro(dot)ru> wrote:
> > Thank you for the catch! Please see the modified version of patch 0004
> > attached.
>
> I tried to review and revise the part related to filters, but I failed
> because I don't understand the notions used in the documentation.
>
> What is the difference between filter expression and filter condition?
> I can guess that filter expression contains question mark,
> parentheses and filter condition inside. But this sentence is in
> contradiction with my guess: "A filter expression must be enclosed in
> parentheses and preceded by a question mark". So, filter expression
> is inside the parentheses. Then what is filter condition? The same?

The SQL standard defines "JSON filter expressions" (in 9.39 of the 2016
edition). It does not use either term "filter condition" nor bare
"filter"; it uses "JSON path predicate" which is the part of the JSON
filter expression that is preceded by the question mark and enclosed by
parens.

Maybe we should stick with the standard terminology ...

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-06-28 05:36:07 Re: An out-of-date comment in nodeIndexonlyscan.c
Previous Message Etsuro Fujita 2019-06-28 04:00:12 Re: Obsolete comment in commands/analyze.c