Re: Order of trigger execution: AFTER DELETE ON EACH ROW doesn't appear to be working properly - Mailing list pgsql-sql

From aklaver@comcast.net (Adrian Klaver)
Subject Re: Order of trigger execution: AFTER DELETE ON EACH ROW doesn't appear to be working properly
Date
Msg-id 101320081908.26623.48F39C9A000855F3000067FF22007613949D0A900E04050E@comcast.net
Whole thread Raw
Responses Re: Order of trigger execution: AFTER DELETE ON EACH ROW doesn't appear to be working properly  ("Christopher Maier" <maier@med.unc.edu>)
List pgsql-sql
 -------------- Original message ----------------------
From: "Christopher Maier" <maier@med.unc.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@comcast.net


pgsql-sql by date:

Previous
From: Tom Lane
Date:
Subject: Re: Order of trigger execution: AFTER DELETE ON EACH ROW doesn't appear to be working properly
Next
From: "Chris Preston"
Date:
Subject: Updating Query of 1 table from data in another