Re: Patch: Improve Boolean Predicate JSON Path Docs

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Cc: Erik Wienhold <ewie(at)ewie(dot)name>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Patch: Improve Boolean Predicate JSON Path Docs
Date: 2023-10-19 05:22:06
Message-ID: CACJufxHaUC=mFzWiR_KfrNdWc0totTqvVYQACJHTP0CT2T5T3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 17, 2023 at 10:56 AM David E. Wheeler <david(at)justatheory(dot)com> wrote:
>
>
> Oh, I thought it would report issues from the files they were found in. You’re right, I forgot a title. Fixed in v4.
>
> David
>

+ Returns the result of a JSON path
+ <link linkend="boolean-predicate-path-expressions">predicate
+ check</link> for the specified JSON value. If the result is
not Boolean,
+ then <literal>NULL</literal> is returned. Do not use with non-predicate
+ JSON path expressions.

"Do not use with non-predicate", double negative is not easy to
comprehend. Maybe we can simplify it.

16933: value. Use only SQL-standard JSON path expressions, not not
there are two "not".

15842: SQL-standard JSON path expressions, not not
there are two "not".

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-10-19 05:26:26 Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written}
Previous Message Peter Smith 2023-10-19 05:17:43 Re: boolin comment not moved when code was refactored