s?
>
> Hmm, I'm not sure. I'm not sure if that's sufficient and that it doesn't
> add any holes, but we can check that.
> At least I think on set default
> triggers we'd need to do something with the check performed from inside
> the trigger.
What's wro
Stephan Szabo wrote:
> On Thu, 17 May 2007, Tom Lane wrote:
>
>> Max Khon <[EMAIL PROTECTED]> writes:
>>> "delete from foo" fails:
>>> ERROR: update or delete on table "bar" violates foreign key constraint
>>> "foobar_fk0&q
> Except that SQL92 at least does seem to say in 11.8 that "All rows that
> are marked for deletion are effectively deleted at the end of the
> SQL-statement, prior to the checking of any integrity constraints." I
> think that likely makes our behavior wrong, but I'm not r
able "foobar"
SQL state: 23503
Detail: Key (bar_id)=(1) is still referenced from table "foobar".
Context: SQL statement "DELETE FROM ONLY "public"."bar" WHERE "foo_id" = $1"
PostgreSQL version: any (I tested on 8.2.4 for Win32 and 8.1.3 fo
