Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Дата
Msg-id 4DE8FD06020000250003E135@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> wrote:

> Would it be possible to dump USING as an equivalent ON condition
> on output (nodeToString), and then examine simple ON conditions to
> turn them into USING conditions on input (stringToNode)?

You know, I'm not necessarily against some warning that a USING
clause in a view definition makes that view more fragile in the face
of schema changes.  If we could invalidate the view at the time of
the schema change, that would not offend me at all.  The two things
which would offend me here are generating a dump which can't be
restored in a single transaction because of errors, or essentially
deprecating the USING clause in general.

-Kevin

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Следующее
От: "dinesh"
Дата:
Сообщение: BUG #6052: ADD COLUMN - ERROR: tables can have at most 1600 columns