Re: AfterTriggerSaveEvent() Error on altered foreign key cascaded delete

Hi,

I am facing the exact same bug when using circular references:

create table m (f1 int primary key, f2 int);
create table s (f2 int primary key, f1 int);
-- Method A --> no error
--alter table s add constraint fkey1 foreign key (f1) references m (f1) on
delete cascade initially deferred;
--alter table m add constraint fkey2 foreign key (f2) references s (f2) on
delete cascade initially deferred;
-- Method B --> error when workaround not used
alter table s add constraint fkey1 foreign key (f1) references m (f1) on
delete cascade on update no action;
alter table s alter constraint fkey1 deferrable initially deferred;
alter table m add constraint fkey2 foreign key (f2) references s (f2) on
delete cascade on update no action;
alter table m alter constraint fkey2 deferrable initially deferred;
-- workaround to fix tgdeferrable and tginitdeferred on delete constraints,
just uncomment next line
-- update pg_trigger set tgdeferrable = false, tginitdeferred = false where
tgtype = 9;
begin transaction;
insert into m values (1,1);
insert into s values (1,1);
commit;
delete from m where f1=1;
drop table s cascade;

The same AfterTriggerSaveEvent() error occurs at the delete command. I found
a workaround to fix the wrong booleans after reading:
https://www.postgresql.org/message-id/8559.1289949074%40sss.pgh.pa.us

Is there any update on this?

best
Martin

--
View this message in context: http://www.postgresql-archive.org/AfterTriggerSaveEvent-Error-on-altered-foreign-key-cascaded-delete-tp5927857p5958509.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.