Allow triggers to fire on records updated or deleted by Referential Integrity CASCADEs

Currently, when a dependent table record is deleted or updated because of a referential integrity CASCADE caused by the delete or update on a parent table, triggers do not fire on that dependent table.

Please allow an option to fire off triggers on a dependent table record deletion or update caused by a referential integrity CASCADEd delete or update. (perhaps also on SET NULL or SET DEFAULT - really, any RI action that changes or deletes data in a dependent row).

Something like:

FOREIGN KEY (...)
REFERENCES MyTable (...)
ON DELETE CASCADE WITH TRIGGERS

I am working on a project now, modernizing a database for one of my client's major applications. I want to define data relationships in the new normalized files, which means using referential integrity.

The client, however, wants all actions on the new data logged to log files (containing record images).
This means using triggers to capture all changes to the data. It also means using an *AFTER *DELETE trigger to capture the image of a deleted record (the modernized application will have savepoint restoration, so these images are important). If I use RI with cascaded deletes, I cannot use a trigger. So, to use the triggers, I cannot use RI, and I instead have to use triggers to simulate RI, using a handcoded definition of the database relationships.

I do not understand why triggers do not fire on RI initiated data changes on dependent files; please allow the option to fire them.