| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: JSON Functions and Operators Docs for v15 |
| Date: | 2022-05-19 14:50:08 |
| Message-ID: | 68025932-0265-60a4-34fc-1c77c813f484@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-05-19 Th 08:19, Justin Pryzby wrote:
>> + same level are considerd to be <firstterm>siblings</firstterm>,
> considered
>
>> + <productname>PostgreSQL</productname> specific functions detailed in
> postgresql hyphen specific (as in the original)
>
> These would all be easier to read with commas:
>
> + <parameter>expression</parameter> is NULL an
> + If <literal>WITH UNIQUE</literal> is specified the
> + If the input is NULL an SQL NULL is returned. If the input is a number
> + If <literal>WITH UNIQUE</literal> is specified there must not
> + is <literal>strict</literal> an error is generated if it yields no items.
>
> There's a few instances of "space space" that could be condensed:
>
> + <function>json_scalar</function> functions, this needs to be either <type>json</type> or
> + which must be a SELECT query returning a single column. If
Thanks, pushed now.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2022-05-19 15:09:35 | 15beta1 crash on mips64el in pg_regress/triggers |
| Previous Message | Tom Lane | 2022-05-19 14:24:46 | Re: bogus: logical replication rows/cols combinations |