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 CACJufxHkBtO8ybU33_W2Sc=YgtZzb6-HAhmqkv6MGYiBG2jxCg@mail.gmail.com
Whole thread Raw
In response to Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions  (jian he <jian.universality@gmail.com>)
Responses Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
List pgsql-hackers
+   <replaceable>context_item</replaceable> can be any character string that
+   can be succesfully cast to <type>jsonb</type>.

typo: "succesfully", should be "successfully"

maybe rephrase it to:
+   <replaceable>context_item</replaceable> can be jsonb type or any
character string that
+   can be successfully cast to <type>jsonb</type>.


+        <literal>ON EMPTY</literal> expression (that is caused by empty result
+        of <replaceable>path_expression</replaceable>evaluation).
need extra white space, should be
+        of <replaceable>path_expression</replaceable> evaluation).



+        The default when <literal>ON EMPTY</literal> or <literal>ON
ERROR</literal>
+        is not specified is to return a SQL NULL value when the respective
+        situation occurs.
Correct me if I'm wrong.
we can just say:
+        The default when <literal>ON EMPTY</literal> or <literal>ON
ERROR</literal>
+        is not specified is to return an SQL NULL value.
Anyway, this is a minor issue.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: walsender.c comment with no context is hard to understand
Next
From: David Rowley
Date:
Subject: Re: Parallel Bitmap Heap Scan reports per-worker stats in EXPLAIN ANALYZE