Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax" - Mailing list pgsql-docs

From Tom Lane
Subject Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"
Date
Msg-id 23093.1585952196@sss.pgh.pa.us
Whole thread Raw
In response to Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: Proposal to improve the content in subsection 8.16.6. "CompositeType Input and Output Syntax"  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-docs
PG Doc comments form <noreply@postgresql.org> writes:
> 1. Replace this:
> "...the whitespace will be ignored if the field type is integer, but not if
> it is text."
> with this:
> "...the whitespace will be ignored if the field type is integer, but not if
> it is a character data type like text."

It's already an example, so I don't see this as an improvement.

> Insert this between the two sentences, i.e. after "...any individual field
> value." and before "You must do so if...":

The proposed additional text is flat-out wrong.

What actually happens here is that text between quotes is considered
quoted (so that, for example, commas within it are not field separators),
but that does not exclude there being other unquoted text within the
same field value.

            regards, tom lane



pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"
Next
From: PG Doc comments form
Date:
Subject: ceil/ceiling/floor mathematical functions documented output is incorrect