Re: CREATE TABLE .. LIKE .. EXCLUDING documentation

Поиск
Список
Период
Сортировка
От Daniel Gustafsson
Тема Re: CREATE TABLE .. LIKE .. EXCLUDING documentation
Дата
Msg-id 30602853-6C83-4BE8-94C9-1FDF796219DF@yesql.se
обсуждение исходный текст
Ответ на Re: CREATE TABLE .. LIKE .. EXCLUDING documentation  (Yugo Nagata <nagata@sraoss.co.jp>)
Ответы Re: CREATE TABLE .. LIKE .. EXCLUDING documentation  (Yugo Nagata <nagata@sraoss.co.jp>)
Список pgsql-hackers
> On 29 Jun 2018, at 07:56, Yugo Nagata <nagata@sraoss.co.jp> wrote:
> On Thu, 28 Jun 2018 16:22:15 -0700
> "David G. Johnston" <david.g.johnston@gmail.com> wrote:

>> ​Maybe try something like:
>>
>> It is legal to specify the same option multiple times - e.g., "INCLUDING
>> option EXCLUDING option" - the outcome is whichever comes last in the
>> command (i.e., in the example, option is excluded).
>
> Certainly. However, it seems to me that example is also redundant.
> I rewrote this as follows:
>
> It is legal to specify multiple options for the same kind of object.
> If they conflict, latter options always override former options.
>
> Does this make sense?

I think this wording makes sense and is clear. Only found a small typo:

+      This is tipically used after <literal>INCLUDING ALL</literal>.

s/tipically/typically/

cheers ./daniel

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rajkumar Raghuwanshi
Дата:
Сообщение: Re: Server crashed with "TRAP: unrecognized TOAST vartag("1", File:"heaptuple.c", Line: 1490)"
Следующее
От: Kuntal Ghosh
Дата:
Сообщение: Re: [WIP] [B-Tree] Retail IndexTuple deletion