Re: Order of trigger execution: AFTER DELETE ON EACH ROW doesn't appear to be working properly

-------------- Original message ----------------------
From: "Christopher Maier" <maier(at)med(dot)unc(dot)edu>
<Snip>

>
> As you can see, doing a row-by-row delete works fine, but when doing a
> bulk delete, all the before triggers are grouped together, as are all
> the after triggers.
>
> Why are these calls not interleaved (e.g. BEFORE DELETE for record 1,
> AFTER DELETE for record 1, BEFORE DELETE for record 2, AFTER DELETE
> for record 2, etc.). Is there any way I can get them to be
> interleaved? This causes problems for my application because if
> dependent rows are not deleted immediately after the row that supports
> it, then I can get "orphaned" rows left in the table that have no
> supporting rows.
>
> Thanks,
> Chris
>

Is not possible to delete the dependent rows from within the BEFORE trigger?

--
Adrian Klaver
aklaver(at)comcast(dot)net