Michael Zouroudis <mzouroudis@idealcorp.com> writes:
> because of integrity constraints, i have to
> delete the record from book_asset, then book, and finally assets. all
> inserts, updates, and deletes are done through the assets table, and i
> have a trigger on assets that first deletes book_asset, then books, and
> finally assets. the problem is when it deletes assets on that third
> delete, it sends the db into a recursive loop(the delete on assets
> starts the trigger again).
Why don't you simply let the system carry on with the deletion that the
trigger was called for?
Seems to me the answer to the problem "my trigger is infinitely
recursive" is "make your trigger not recurse".
regards, tom lane