Re: CREATE TABLE .. LIKE .. EXCLUDING documentation
От | Tom Lane |
---|---|
Тема | Re: CREATE TABLE .. LIKE .. EXCLUDING documentation |
Дата | |
Msg-id | 26676.1530290650@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: CREATE TABLE .. LIKE .. EXCLUDING documentation (Daniel Gustafsson <daniel@yesql.se>) |
Ответы |
Re: CREATE TABLE .. LIKE .. EXCLUDING documentation
Re: CREATE TABLE .. LIKE .. EXCLUDING documentation |
Список | pgsql-hackers |
Daniel Gustafsson <daniel@yesql.se> writes: >> On 29 Jun 2018, at 15:42, Peter Eisentraut <peter.eisentraut@2ndquadrant.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). +1 for shortening it as proposed by Peter. The existing arrangement made sense when it was first written, when there were only about three individual options IIRC. Now it's just confusing, especially since you can't tell very easily whether any of the individual options were intentionally omitted from the list. It will not get better with more options, either. regards, tom lane
В списке pgsql-hackers по дате отправления: