| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Rudy Koento <rudy_koento(at)yahoo(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: updating data but the constraint is set "immediate" |
| Date: | 2003-07-01 16:09:58 |
| Message-ID: | 20030701090442.G54301-100000@megazone23.bigpanda.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Barwick | 2003-07-01 19:39:08 | Re: Accent insensitive search |
| Previous Message | Alejandro Javier Pomeraniec | 2003-07-01 15:11:54 | Accent insensitive search |