Re: Q: Database Trigger definition in Oracle 7.3

From: Jonathan Gennick <gennick_at_worldnet.att.net>
Date: Sun, 26 Jul 1998 17:39:36 GMT
Message-ID: <6pfpl6$ank@bgtnsc03.worldnet.att.net>

On Thu, 23 Jul 1998 08:51:59 +0200, Frank Pohl <frank.pohl.fp_at_bayer-ag.de> wrote:

>Question 1:
>I want to create multiple triggers for the same event, e.g. for the
>Update and Insert. The reason is, I want to separate the different
>functions to be executed form each other.
>Is the performance much better with one than with multiple triggers ?

I don't believe it will matter much. Multiple triggers were allowed because Oracle's replication features creates triggers, and Oracle needed to keep them seperate from user triggers.

>Question 2:
>Is it better to define the columns which fire the trigger in
>the trigger code (with If UPDARTING('...') or to do this in the trigger
>defintion.

Generally, if I only want a trigger to fire when certain columns are updated, I specify that in the trigger definition. It seems like the most straightforward approach (my opinion), and I would think you would save something because the trigger is not fired when those columns don't change.

regards,

Jonathan Received on Sun Jul 26 1998 - 12:39:36 CDT