Re: updating data but the constraint is set "immediate"

#1

--- Bruno Wolff III <bruno (AT) wolff (DOT) to> wrote:

Quote:

On Tue, Jul 01, 2003 at 02:35:48 -0700,
Rudy Koento <rudy_koento (AT) yahoo (DOT) com> wrote:
Hi,

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).

Is there anyway I can circumvent this? I
remembered I
can delete using pgAdminII. However, I don't have
a
windows box now, and therefore I can't use
pgAdminII.

You can use alter table to drop the constraint and
then to add the corrected
constraint. I am not sure if this was available
prior to 7.3.

I solved it by using pgAdminII remotely through ssh
port forwarding. I'm curious though, as to why does
pgAdminII is able to defer the constraints whereas
using command line cannot...

__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: updating data but the constraint is set "immediate"

comp.databases.postgresql.general comp.databases.postgresql.general

Re: updating data but the constraint is set "immediate" - 07-01-2003 , 10:03 PM