Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"

On Mon, Apr 6, 2020 at 12:46 AM Bryn Llewellyn wrote: > Tom Lane wrote: > > ... > > > It's already an example, so I don't see this as an improvement. > > ... > > > The proposed additional text is flat-out wrong. > > What actually happens here is that text between quotes is considered > quoted

Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"

Tom Lane wrote:...It's already an example, so I don't see this as an improvementThe proposed additional text is flat-out wrong.What actually happens here is that text between quotes is consideredquoted (so that, for example, commas within it are not field separators),but

Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"

PG Doc comments form 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

Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax"

The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/rowtypes.html Description: 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