| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | b(dot)l(dot)michielsen(at)wanadoo(dot)fr |
| Subject: | Inconsistency in: 2.3. Creating a New Table |
| Date: | 2023-12-20 23:35:38 |
| Message-ID: | 170311533858.1876504.6571296569439176220@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/tutorial-table.html
Description:
The text in: 2.3. Creating a New Table, states:
"... you can type the command aligned differently than above, or even all on
one line. Two dashes (“--”) introduce comments. Whatever follows them is
ignored up to the end of the line ..."
The last phrase contradicts the first one. If there is a comment on a
column definition you cannot continue to define a new column on the same
line. It looks like commas were column separators before comments were
allowed to appear. They rather should have become column terminators
appearing after an optional comment?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-12-22 16:06:09 | Documentation does not describes format for access privileges: =Tc/user |
| Previous Message | Daniel Gustafsson | 2023-12-19 11:07:47 | Re: 'bar' shouldn't be a string in example |