| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE .. LIKE .. EXCLUDING documentation |
| Date: | 2018-06-29 13:49:10 |
| Message-ID: | B3A6CB65-3E28-47CE-97AF-FCEAA44600A6@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 29 Jun 2018, at 15:42, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> While we're here, do people find this useful:
>
> <para>
> <literal>INCLUDING ALL</literal> is an abbreviated form of
> <literal>INCLUDING COMMENTS INCLUDING CONSTRAINTS INCLUDING
> DEFAULTS INCLUDING IDENTITY INCLUDING INDEXES INCLUDING STATISTICS
> INCLUDING STORAGE</literal>.
> </para>
>
> Maybe something more like "... is an abbreviated form selecting all the
> available individual options”.
While quite a mouthful, I do find the former quite clear. Your suggestion
clearly reads better, but I would personally scroll back up to the Synopsis to
see the list if it wasn't easily available in the paragraph (but that’s all
personal preference).
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mai Peng | 2018-06-29 14:00:44 | ERROR: cannot start subtransactions during a parallel operation |
| Previous Message | Peter Eisentraut | 2018-06-29 13:42:49 | Re: CREATE TABLE .. LIKE .. EXCLUDING documentation |