Re: insert or update violates foreign key constraint.why?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Oleg Mayevskiy <oleg(dot)mayevskiy(at)s2002(dot)tu-chemnitz(dot)de>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: insert or update violates foreign key constraint.why?
Date: 2004-06-01 02:05:11
Message-ID: 14140.1086055511@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Oleg Mayevskiy <oleg(dot)mayevskiy(at)s2002(dot)tu-chemnitz(dot)de> writes:
> it seems to be a simple problem, but it is not.

Yes it is ... you're expecting the RI triggers to fire during the
plpgsql function, but in fact they fire at completion of the outer
statement that called the plpgsql function.

There's been some debate about whether this is really the most
desirable behavior, but that's how it is at the moment.

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message email lists 2004-06-01 12:29:04 assistance on self join pls
Previous Message Jaime Casanova 2004-05-31 14:19:49 joining a table with a function