Re: COPY options

Поиск
Список
Период
Сортировка
От Andrei M. Eichler
Тема Re: COPY options
Дата
Msg-id CABS=F1+WaN1wXgDY1b+DMOTgGqgWjAoeMuZUiH5zOWVYO+A7gw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: COPY options  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-docs
Thanks for the replies, I'm using postgres since 8.3 and didn't notice at the time of 9.0 release the change in the syntax, as the old syntax still works, every time I read the current documentation I didn't notice that I was using it wrong.

I agree with Tom Lane about leaving it alone.

Another question, I don't know if I should ask it here, why FORCE_NOT_NULL and FORCE_NULL doesn't allow * as list of columns as FORCE_QUOTE?

2016-04-29 13:03 GMT-03:00 Tom Lane <tgl@sss.pgh.pa.us>:
Kevin Grittner <kgrittn@gmail.com> writes:
> It's not really a question of whether we should go back to
> documenting the deprecated syntax, but whether (and when) support
> for it should finally be ripped out.  It was last documented in 8.4.

We still document, and support, not only the pre-9.0 COPY syntax but
also the pre-7.3 COPY syntax; see the bottom of the COPY reference page.
The timescale for getting rid of that kind of thing is *really* long,
in part for fear of breaking old pg_dump backups.

BTW, so far as FORCE NULL goes, I think that feature was implemented
earlier in the 9.0 cycle than where we put in the new generalized
option syntax.  When we did the latter, we reverted the documentation
of the old syntax to exactly match 8.4, but did not take out the
gram.y production allowing the never-released FORCE NULL syntax.
I do not recall if that was intentional or an oversight.
We could (a) document it, (b) remove it, or (c) leave it alone.
At this point I favor the benign neglect approach.

                        regards, tom lane

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

Предыдущее
От: "Andrei M. Eichler"
Дата:
Сообщение: Re: Date formatting
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: 36.1 Overview of Trigger Behavior