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

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
Date: 2024-07-08 03:18:23
Message-ID: CACJufxHkBtO8ybU33_W2Sc=YgtZzb6-HAhmqkv6MGYiBG2jxCg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-07-08 03:43:01 Re: Parallel Bitmap Heap Scan reports per-worker stats in EXPLAIN ANALYZE
Previous Message Amit Kapila 2024-07-08 03:16:19 Re: walsender.c comment with no context is hard to understand