Re: Oracle direction on triggers

On 24 Feb 2003, rs_arwar_at_hotmail.com wrote:

> I personally like to avoid triggers for couple of reasons.
>
> 1) A disabled trigger does not complain unless manually enabled. So if
> a trigger is disabled for whatever reason and you are
> inserting/updating records in your table thinking trigger is doing
> it's job, it is actually fast asleep.
>
> 2) If you are using triggers to do integrity check, then you can
> multiply the above scenario by whatever the damage a bad row of data
> may cause.

I'm not sure I understand. A view that's been recompiled with different SQL but still returns the same columns doesn't notify the calling process either. Maybe you shouldn't allow the trigger to be disabled?

-- 
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.