Triggers and RDBM's

[Robert Mills]

I was a DBA for nearly 5 years in the City-of-London and I loved triggers for several reasons:
 
1. Not if the DBA maintains the triggers.
2. Don't try testing against the production database.
3. What the can't see they can't !"£$% up.
4. Bad design causes that. Set up 'rules' that can not be broken (improved security)!!
5. Never had any problems myself.
6. Common database code is held in one place (the database) instead of several programs. Change it in one place not many!! And no recompile required <bliss>.
etc.
 
regards, 
  
Robert W.Mills 
MIS Systems Development Manager 
Pinnacle Arvato 
+44 (0)20 8309 3604 
 

  _____  

From: powerh-l-bounces+robert.mills=pinnaclearvato.co.uk at lists.sowder.com [mailto:powerh-l-bounces+robert.mills=pinnaclearvato.co.uk at lists.sowder.com] On Behalf Of Robert Edis
Sent: 30 October 2006 15:38
To: powerh-l at lists.sowder.com
Subject: Re: Triggers and RDBM's



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/18cc3b9d/attachment.htm