Triggers and RDBM's

[Robert Edis]

My inderstanding is that DBA's hate triggers for several reasons:

1. they are difficult to keep track of and it is easy to create trigger 
loops.  I.e. trigger A causes trigger B to fire which causes trigger C to 
fire which causes trigger A to fire.
2. they generally can't be over-ridden for test cases, debugging, or 
special cases.
3. are "hidden" from the developers.
4. have security implications.  E.g. a user doesn't have update access to 
a table but the application they use can fire the trigger.  Use of the 
trigger bypasses the user security and allows the user to update the 
table.
5. difficult to tune database for performance if it has lots of triggers.
etc.

Bluey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20061030/755ea135/attachment.html