Re: BUG #10856: Delete trigger corrupts foreign key integrity
От
Greg Stark
Тема
Re: BUG #10856: Delete trigger corrupts foreign key integrity
Дата
Msg-id
CAM-w4HOCxde9LV_j8ipvLSwojQQ-6Mf0Fy0U=J=CZqCOYxs13w@mail.gmail.com
Ответ на
BUG #10856: Delete trigger corrupts foreign key integrity (m.fritz@wisutec.de)
Список
Дерево обсуждения
BUG #10856: Delete trigger corrupts foreign key integrity m.fritz@wisutec.de
Re: BUG #10856: Delete trigger corrupts foreign key integrity Greg Stark <stark@mit.edu>
Re: BUG #10856: Delete trigger corrupts foreign key integrity Tom Lane <tgl@sss.pgh.pa.us>
On 5 Jul 2014 06:58, wrote: > > A "before delete" trigger on a child table returning "NULL" prevents records > from deletion, which violates against the FOREIGN KEY constraint. Child > records are still present, master record is deleted but FOREIGN KEY is still > "VALID". Yup, don't do that. I bellringer there are warnings to this effect in the documentation. PostgreSQL's referential integrity is handled by triggers so it's possible to escape their effects with other triggers. We could implement them internally without using triggers but there are other advantages to using triggers and so far the feeling is that the development effort is better spent elsewhere.
В списке pgsql-bugs по дате отправления