Not quite as expected. I didn't expect deleting the 2 from the
primary table to fail because the CASCADE DELETE wasn't able to run on
the second (even though no values existed in that table). I suppose
it does run properly (blocks all delete attempts) -- but I just didn't
expect it to error out on values which didn't exist in the second
table -- thereby blocking the deletion from the primary or referred
table..
Tried against 7.1beta3 and 7.1beta5.
--
Rod Taylor
There are always four sides to every story: your side, their side, the
truth, and what really happened.
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Rod Taylor" <rbt@zort.ca>
Cc: "Hackers List" <pgsql-hackers@postgresql.org>
Sent: Friday, April 06, 2001 1:54 AM
Subject: Re: [HACKERS] Foreign Key & Rule confusion WAS: Lost
Trigger(s)?
> "Rod Taylor" <rbt@zort.ca> writes:
> > Found the issue. Try out the attached SQL in a fresh database.
>
> And? AFAICT it behaves as expected, in either 7.0.2 or current ...
>
> regards, tom lane
>