Re: nchar is undocumented

Erik Wienhold <ewie@ewie.name>

From: Erik Wienhold <ewie@ewie.name>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: David Rowley <dgrowleyml@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-docs@lists.postgresql.org
Date: 2024-05-06T13:42:56Z
Lists: pgsql-docs
On 2024-05-06 10:59 +0200, Alvaro Herrera wrote:
> By the way, this neighboring sentence is a bit awkward
> 
> " It must be ... or a type for which there is a cast from json to that type."
> 
> Would it be better to say
>   " It must be ... or a type to which a cast from json exists."
> ?

Yeah, that sounds better, but I'd say:
    "[...] or a type _for_ which a cast from json exists."

Or maybe just
    "[...] or any type that can be cast to json."
?

-- 
Erik



Commits

  1. Minor wording change in table "JSON Creation Functions"

  2. Remove mention of nchar