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

From: "Connor McDonald" <mcdonald.connor@xxxxxxxxx>
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Date: Wed, 3 Sep 2008 21:49:47 +0800

And one thing I forgot....shucks, Oracle, how hard can it be to implement

*alter table T modify C default SEQ.NEXTVAL*

That would eliminate half the triggers floating around out there in one
swoop...


On Wed, Sep 3, 2008 at 9:48 PM, Connor McDonald
<mcdonald.connor@xxxxxxxxx>wrote:

> In perhaps a perverse way, I'd be bigger fan of triggers if you could *not*
> disable them...Then people would have to *really* sit down and think about
> whether the trigger they are about to implement is a genuine implementation
> of a rule (eg audit, complex constraint) versus a convenience that
> could/should have been coded in the application ...
>
> I always find it hilarious when you have to wear the day-to-day hit of
> capturing changes to every row on every row due to some "cast hard in
> concrete business rule of - thou shalt audit everything" ....but then take a
> system outage because a large scale data change has to occur, and the same
> people then insert ...*"but we don't want to audit that*" comes along the
> line...
>
> --
> Connor McDonald
> ===========================
> email: connor_mcdonald@xxxxxxxxx
> web: http://www.oracledba.co.uk
>
> "Semper in excremento, sole profundum qui variat"
>
>


-- 
Connor McDonald
===========================
email: connor_mcdonald@xxxxxxxxx
web: http://www.oracledba.co.uk

"Semper in excremento, sole profundum qui variat"

Follow-Ups:
- Re: "All triggers are evil",..., really?
  - From: Niall Litchfield

References:
- Re: "All triggers are evil",..., really?
  - From: Connor McDonald

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

Other related posts: