From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: self-referential UPDATE problem on 7.4 |
Date: | 2007-01-04 17:58:44 |
Message-ID: | 20070104175844.GE3969@merkur.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Jan 04, 2007 at 06:37:23PM +0100, Karsten Hilbert wrote:
> > > It returns "UPDATE 2" which is what I expect from the data.
> > > However, the rows in question are not actually updated.
> >
> > That seems very strange. Could you perhaps have a BEFORE UPDATE trigger
> > that's changing the values back to null again?
> I do but I drop that one in the script before doing the
> above update. I may have an old one hanging around, though,
> I'll double-check.
I was missing a schema qualification in a drop statement,
hence the culprit trigger function wasn't dropped properly.
Sometimes a hint helps.
Thanks Tom,
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Madison Kelly | 2007-01-04 18:10:53 | Re: pg_dump question |
Previous Message | Devrim GUNDUZ | 2007-01-04 17:42:31 | Re: pg_dump question |