New answers tagged constraint
It is not possible with a constraint. Have a look at Multiple Cascading Actions. No table can appear more than one time in the list of all cascading referential actions that result from the DELETE or UPDATE. You can use an instead of trigger instead where you do the update in Table2 before the delete in Table1. The trigger could look something like ...
Top 50 recent answers are included