Hi,
maybe I am completely off topic but I have been out off office for a while.
I have a trigger that just set a timestamp value after insert and update
without recursivity.
CREATE TRIGGER TSTEST FOR DBA.TEST AFTER INSERT,UPDATE EXECUTE (
UPDATE DBA.TEST SET TS = TIMESTAMP WHERE ID = :NEW.ID IGNORE TRIGGER;
)
The "IGNORE TRIGGER" clause prevent and endless loop. Without it, the server
crash...
Yves
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of John Holland
Sent: 21 janvier, 2002 14:05
To: [EMAIL PROTECTED]
Subject: trigger recursiveness
hi,
what happens when a (for example) a update trigger on table t1 fires a
further update trigger on t1 and so on. could that cause an endless
loop? and if so, how can the chain be broken?
i rember reading something about this particular subject once. and i
think that there was a specific statement within the trigger which can
determine if the trigger was in affect (indirectly) fired from another.
i'm not sure but, i think elke had answered this one.
thanx in advance,
john
[EMAIL PROTECTED]
[EMAIL PROTECTED]
