Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions - Mailing list pgsql-hackers

From jian he
Subject Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
Date
Msg-id CACJufxFXJr61cxCBYBRhuU__S5YmdnGfHO8G2J7tYs0wbUODYQ@mail.gmail.com
Whole thread Raw
In response to Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
List pgsql-hackers
On Mon, Jul 8, 2024 at 8:57 PM Amit Langote <amitlangote09@gmail.com> wrote:
>
> Updated patch attached.
>

         Returns true if the SQL/JSON <replaceable>path_expression</replaceable>
-        applied to the <replaceable>context_item</replaceable> using the
-        <literal>PASSING</literal> <replaceable>value</replaceable>s yields any
-        items.
+        applied to the <replaceable>context_item</replaceable> doesn't yield
+        any items.
should "doesn't" be removed?
should it be "yields"?


+        set. The <literal>ON ERROR</literal> clause specifies the behavior
+        if an error occurs when evaluating
<replaceable>path_expression</replaceable>,
+        when coercing the result value to the
<literal>RETURNING</literal> type,
+        or when evaluating the <literal>ON EMPTY</literal> expression if the
+        <replaceable>path_expression</replaceable> evaluation results in an
+        empty set.
last sentence, "in an empty set." should be "is an empty set"


Other than that, it looks good to me.



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: Parallel CREATE INDEX for GIN indexes
Next
From: Junwang Zhao
Date:
Subject: Re: jsonpath: Inconsistency of timestamp_tz() Output