Re: updating data but the constraint is set "immediate" - Mailing list pgsql-general

From Stephan Szabo
Subject Re: updating data but the constraint is set "immediate"
Date
Msg-id 20030701090442.G54301-100000@megazone23.bigpanda.com
Whole thread Raw
In response to updating data but the constraint is set "immediate"  (Rudy Koento <rudy_koento@yahoo.com>)
List pgsql-general
On Tue, 1 Jul 2003, Rudy Koento wrote:

> I've realised that my tables' constraint was set to
> IMMEDIATE.  So, when I update one table, there's error
> because of referential integrity.  Reading the docs, I
> read that SET CONSTRAINTS has no effect on IMMEDIATE
> (and I've confirmed that by trying it out).

Actually SET CONSTRAINTS has no effect on NOT DEFERRABLE
constraints (which is the default for initially immediate
iirc but not required).

> Is there anyway I can circumvent this?  I remembered I

The best way is probably to drop and re-add the constraint
with the attributes you want (possibly deferrable initially
immediate if you want to be normally immediate but with the
possibility of set constraints)



pgsql-general by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: updating data but the constraint is set "immediate"
Next
From: Jan Wieck
Date:
Subject: New position and new location