From: | Rudy Koento <rudy_koento(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: updating data but the constraint is set "immediate" |
Date: | 2003-07-02 03:03:10 |
Message-ID: | 20030702030310.6593.qmail@web41609.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
--- Bruno Wolff III <bruno(at)wolff(dot)to> wrote:
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2003-07-02 03:06:02 | Re: postgresql.org is unreliable |
Previous Message | Joe Conway | 2003-07-02 01:57:49 | Re: ERROR: language "c" is not trusted |