Re: "All triggers are evil",..., really?

From: Andrew Kerber <>
Date: Thu, 21 Aug 2008 07:32:31 -0500
Message-ID: <>

How many people remember ERwin? If you created the default triggers with that software, one of the 'helpful' things those triggers would do is handle your foreign key constraints. By helpfully adding the required foreign key entry. I could never figure that one out.

On Thu, Aug 21, 2008 at 4:33 AM, Amar Padhi <> wrote:

> I have personally avoided Triggers but I know they are sometimes the only
> available alternative or short-cut. During design/development stage, we
> ensure that the technical design does not rely on triggers, but proper
> routines that are put in place for required business logic (except extreme
> cases such as audit requirements etc.). From my experience, going for a
> trigger would mean that developers have lost track of how and from where the
> base table is getting hit, and yes this does happen as the support team
> looses control of the changes being done to the system.
> Apart from the trigger-disable aspect discussed earlier, trigger code
> cannot be wrapped either. I know of a case where a client developers took
> advantage of modifying open trigger code and messed up the data.
> I know of another system that has reached its support limits because of
> excessive use of triggers. Identifying the process logic or the business
> flow is a very cumbersome job on this system. Making changes in this system
> often results in conflict that cannot be tested before hand.
> Avoding trigger can be a good practice but not rule of thumb.
> --
> Thanks!
> Amar Kumar Padhi
> Oracle DBA/Architect

Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Received on Thu Aug 21 2008 - 07:32:31 CDT

Original text of this message