Re: Doc Rework: Section 9.16.13 SQL/JSON Query Functions
Erik Rijkers <er@xs4all.nl>
From: Erik Rijkers <er@xs4all.nl>
To: Amit Langote <amitlangote09@gmail.com>,
jian he <jian.universality@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-07-05T13:16:12Z
Lists: pgsql-hackers
Op 7/5/24 om 14:35 schreef Amit Langote:
> Hi Jian,
>
> Thanks for the reviews.
>
> [v3-0001-SQL-JSON-Various-improvements-to-SQL-JSON-query-f.patch]
i.e., from the patch for doc/src/sgml/func.sgml
Small changes:
4x:
'a SQL' should be
'an SQL'
('a SQL' does never occur in the docs; it's always 'an SQL'; apperently
the 'sequel' pronunciation is out)
'some other type to which can be successfully coerced'
'some other type to which it can be successfully coerced'
'specifies the behavior behavior'
'specifies the behavior'
In the following sentence:
"By default, the result is returned as a value of type <type>jsonb</type>,
though the <literal>RETURNING</literal> clause can be used to return
the original <type>jsonb</type> value as some other type to which it
can be successfully coerced."
it seems to me that this phrase is better removed:
"the original <type>jsonb</type> value as"
thanks,
Erik
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
SQL/JSON: Various improvements to SQL/JSON query function docs
- ce416fadb4b6 17.0 landed
- 42de72fa7b80 18.0 landed