Re: COPY manual is ambiguous about column list
От | Bruce Momjian |
---|---|
Тема | Re: COPY manual is ambiguous about column list |
Дата | |
Msg-id | 20191220134541.GB29807@momjian.us обсуждение исходный текст |
Ответ на | Re: COPY manual is ambiguous about column list ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: COPY manual is ambiguous about column list
|
Список | pgsql-docs |
On Thu, Dec 19, 2019 at 10:33:48PM -0700, David G. Johnston wrote: > On Thursday, December 19, 2019, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > "David G. Johnston" <david.g.johnston@gmail.com> writes: > > Seems better to simply talk about each form independently: > > > If a list of columns is specified, <command>COPY TO</command> will only > > copy the data in the specified columns to the file. <command>COPY > > FROM</command> will, by position (i.e., the number of columns listed must > > match the number of columns in the file), match each file column to the > > named column in the table. Any additional columns present in the table > > will receive their default value. > > +1 for separating it like that, but your middle sentence reads awkwardly > to me. How about something like > > <command>COPY FROM</command> will match each listed column in the table > to a file column by position (so the number of columns listed must match > the number of columns in the file). > > > > > +1 OK, how is this? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
Вложения
В списке pgsql-docs по дате отправления: