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

From: "Jared Still" <jkstill@xxxxxxxxx>
To: toon@xxxxxxxxxxx
Date: Wed, 20 Aug 2008 09:52:38 -0700

On Wed, Aug 20, 2008 at 6:32 AM, Toon Koppelaars <toon@xxxxxxxxxxx> wrote:

> I need to get this of my chest....
>
>
And I, this.

In the article of interest at
http://www.oracle.com/technology/oramag/oracle/08-sep/o58asktom.html
Tom explains that a package and 3 triggers can be used to avoid the problem
that the developers created for themselves by the use of this trigger.

The problem is actually more fundamental than that.

The 3 triggers and a package solution (or compound trigger in 11g) is
actually a crutch required to deal with a poorly designed database.
I have in fact used that 'solution' to enforce logic in an intentionally
poorly designed database as part of a presentation on normalization.

It's a nice trick to have have up your sleeve if dealing with a schema that
cannot be changed, but is still a poor substitute for properly designed
databases.

-- 
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

References:
- "All triggers are evil",..., really?
  - From: Toon Koppelaars

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

Other related posts: