Re: Patch: Improve Boolean Predicate JSON Path Docs

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@justatheory.com>
Cc: Erik Wienhold <ewie@ewie.name>, pgsql-hackers@lists.postgresql.org
Date: 2024-01-25T16:03:24Z
Lists: pgsql-hackers
"David E. Wheeler" <david@justatheory.com> writes:
> On Jan 24, 2024, at 16:32, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> +      <para>
>> +       Predicate check expressions are required in the
>> +       <literal>@@</literal> operator (and the
>> +       <function>jsonb_path_match</function> function), and should not be used
>> +       with the <literal>@?</literal> operator (or the
>> +       <function>jsonb_path_exists</function> function).
>> +      </para>
>> +     </note>
>> +    </sect4>

> I had this bit here:

>       <para>
>        Conversely, non-predicate <type>jsonpath</type> expressions should not be
>        used with the <literal>@@</literal> operator (or the
>        <function>jsonb_path_match</function> function).
>       </para>

I changed the preceding para to say "... check expressions are
required in ...", which I thought was sufficient to cover that.
Also, the tabular description of the operator tells you not to do it.

> What do you think of also dropping the article from all the references to “the strict mode” or “the lax mode”, to make them “strict mode” and “lax mode”, respectively?

Certainly most of 'em don't need it.  I'll make it so.

			regards, tom lane



Commits

  1. Doc: improve documentation for jsonpath behavior.

  2. Ensure we have a snapshot while dropping ON COMMIT DROP temp tables.