NOT DEFERRABLE as default, why and how to manage it.

Поиск
Список
Период
Сортировка
От Ivan Sergio Borgonovo
Тема NOT DEFERRABLE as default, why and how to manage it.
Дата
Msg-id 20080819100111.07c683ff@dawn.webthatworks.it
обсуждение исходный текст
Ответы Re: NOT DEFERRABLE as default, why and how to manage it.  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-general
I just learnt that NOT DEFERRABLE is default.
I vaguely understand that generally stricter policies protect
distracted programmers from making mistakes... but missing an "alter
constraint" it makes refactoring a PITA.

Is it mandated by SQL standard?
Any other rational reason to make NOT DEFERRABLE default?

Is there any shortcut if I've to change to deferrable most of my
constraints?

Other than pgfoundry is there any other recipe repository where to
look for refactoring tools for postgresql?

--
Ivan Sergio Borgonovo
http://www.webthatworks.it


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

Предыдущее
От: "Dave Page"
Дата:
Сообщение: Re: PostgreSQL on Windows x64
Следующее
От: tuanhoanganh
Дата:
Сообщение: Pg dump Error