Its my plan in fact, it was to make some optimisation, because i need to
copy all the test from the BEFORE statement to the AFTER.
Thx for your help,
Regards,
Tom Lane wrote:
>
> "Froggy / Froggy Corp." <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> This is a really badly designed trigger
"Froggy / Froggy Corp." <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This is a really badly designed trigger anyway: why don't you just
>> modify the NEW row, instead of incurring orders of magnitude more work
>> by launching an entire new SQL command?
> I make some reorganization of my table
Tom Lane wrote:
>
> "Froggy / Froggy Corp." <[EMAIL PROTECTED]> writes:
> > PG7 dont make recursiv, it wait for the end of the trigger BEFORE_UPDATE
> > to call the new UPDATE stat and forgot the 3rd AFTER_UPDATE. PG8 is
> > better, it call trigger like real recursiv fonction, but allways dismiss
"Froggy / Froggy Corp." <[EMAIL PROTECTED]> writes:
> PG7 dont make recursiv, it wait for the end of the trigger BEFORE_UPDATE
> to call the new UPDATE stat and forgot the 3rd AFTER_UPDATE. PG8 is
> better, it call trigger like real recursiv fonction, but allways dismiss
> the 3rd AFTER UPDATE.
Th
