Cascading delete problem
437542Apr 9 2009 — edited Apr 11 2009I need a cascading delete but I can't do it by defining constraints with ON DELETE CASCADE because of a requirement to check priviledges in triggers that raises mutation complaints when trying to delete master and details in the same transaction. It must be done in the application.
In Forms I would do it in a pre-delete trigger. What would be the best ApEx equivalent that is "minimally invasive", augmenting the standard automatic row processing and not replacing it? If I define a delete details process that executes before the standard DML process, is it going to get rolled back if there's an error in the standard DML?