If you neglect situations like system crashes, or power failure, is it possible in the system, that under any circumstances an after insert trigger is not fired? If so, what circumstances would lead to such an effect?
(I know that LOAD TABLE, TRUNCATE, and WRITETEXT will not fire triggers)
asked 24 Mar '11, 06:56
Well, I'm not sure whether you ask about a trigger that should fire, and does not in a particular situation, or ask more generally.
In addition to Thomas's answer, there are a few more situations I'm aware of:
EDIT: Sorry, I should have read your question better - so, w.r.t. AFTER INSERT triggers, only point one could be a reason.
As to the reliability of triggers, I do rely on them. To quote from the CREATE TRIGGER page:
As such, as far as triggers are not explicitely prevented (s.a.), they should work in an atomic way.
That being said, I would only use triggers for tasks that cannot be handled by other features like
As Breck wrote in his well-knwon book: '"Avoid writing triggers." - " - if possible"*, I would add:)
Not a answer to your question but I know that an AFTER UPDATE Trigger is not fired when content of the fields in the row is not changed.
A statement like
will not force the execution of an after update trigger.
answered 24 Mar '11, 07:31