I can't answer your question but I think you may have a serious
database design issue at hand.
Why not try to accomplish your goals in a simpler way?
Regards,
Ivan Pavlov
On Dec 15, 12:49 pm, ket...@ketema.net (Ketema Harris) wrote:
> I am interested in finding out the pros, cons, pitfalls of using the
> following design:
>
> Manual insert into Table A.
> Table A has a BEFORE INSERT trigger that causes an insert to table B.
> Table B has an AFTER INSERT trigger that causes an insert back to
> table A (With different criteria not an endless loop)
>
> Table A will have its Before Trig fire again and this time the
> criteria causes it to finish with a return new.
>
> Will the second insert into table A commit before the first insert
> into table A? What order does the insert into table B finish up?
>
> Ketema J. Harriswww.ketema.net
> ket...@ketema.net
> ketemaj on iChat
>
> --
> Sent via pgsql-general mailing list (pgsql-gene...@postgresql.org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general