2008/12/15 Ketema Harris :
> 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
>
On 16/12/2008 16:26, Ketema wrote:
> automatically after certain input. In analyzing the task I saw two
> main paths. Use the trigger and rule system that Pg provides or
> construct external methods to control the logic and issue "simple"
> commands to insert data when appropriate. I chose to us
On Dec 16, 10:31 am, Ivan Pavlov wrote:
> 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 a
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 us
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 en
