Horton
Menu

Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions

jian he <jian.universality@gmail.com>

View thread
From: jian he <jian.universality@gmail.com>
To: Amit Langote <amitlangote09@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-07-08T03:18:23Z
Lists: 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.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. SQL/JSON: Various improvements to SQL/JSON query function docs