Re: [GENERAL] plperl function called > once in cascading triggers

2007-03-15 Thread Kenneth Downs
Martijn van Oosterhout wrote: On Wed, Mar 14, 2007 at 08:09:24PM -0400, Kenneth Downs wrote: What I have noticed is that once the innermost instance exits, none of the outer instances execute any further, suggesting that the plperl routine is not "re-entrant" (if I am using that term correct

Re: [GENERAL] plperl function called > once in cascading triggers

2007-03-15 Thread Martijn van Oosterhout
On Wed, Mar 14, 2007 at 08:09:24PM -0400, Kenneth Downs wrote: > What I have noticed is that once the innermost instance exits, none of > the outer instances execute any further, suggesting that the plperl > routine is not "re-entrant" (if I am using that term correctly). Doesn't sound right, do

[GENERAL] plperl function called > once in cascading triggers

2007-03-14 Thread Kenneth Downs
Consider the case where an AFTER STATEMENT trigger calls a plperl function which performs a loop. Inside of the loop it updates at least one other table. The table being updated has an AFTER STATEMENT trigger that calls the same plperl function (w/different parms of course), which goes into