[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [HACKERS] ENABLE/DISABLE CONSTRAINT NAME
From:       Fabien COELHO <coelho () cri ! ensmp ! fr>
Date:       2013-08-30 18:57:45
Message-ID: alpine.DEB.2.02.1308302052500.14562 () localhost6 ! localdomain6
[Download RAW message or body]


> Uh ... why not just drop the constraint, and re-add it later if you want
> it again?

My 0.02¤ : maybe because you must keep track of the constraint details to 
do so, this it is significantly more error prone than disable / enable 
when the bookkeeping is done by the system and if everything is in a 
transaction... If the ENABLE is automatically done on the next COMMIT, 
that would be even better.

> This seems like adding a lot of mechanism (and possible bugs) for a 
> rather marginal use-case.

That is possible!

-- 
Fabien.
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
[prev in list] [next in list] [prev in thread] [next in thread]