The following sql demonstrates the problem. What I'm getting at here is
cases where the rows in "b" are being altered instead of being deleted
consequently the delete to "a" shouldn't happen.
create table a (id int4 primary key);
create table b (id int4 references a on delete cascade);
create rule b0 as on delete to b do instead nothing;
insert into a values (1);
insert into b values (1);
delete from a;
Joshua b. Jore ; http://www.greentechnologist.org
On Wed, 12 Jun 2002, Joshua b. Jore wrote:
> I found the function in src/backend/utils/adt/ri_triggers.c. A previous
> note in the archives says it might be an invalid SPI command/statement. So
> how do I debug that? Which traces ought to be turned on?
>
> Joshua b. Jore ; http://www.greentechnologist.org
>
>