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

From: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
To: pgsql-general(at)postgresql(dot)org
Subject: NOT DEFERRABLE as default, why and how to manage it.
Date: 2008-08-19 08:01:11
Message-ID: 20080819100111.07c683ff@dawn.webthatworks.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message tuanhoanganh 2008-08-19 08:09:31 Pg dump Error
Previous Message Dave Page 2008-08-19 07:50:57 Re: PostgreSQL on Windows x64