Re: Oracle Stored Procedures

"Knut Talman" <knut.talman_at_mytoys.de> wrote in message news:3B0278BB.4943E63A_at_mytoys.de...
> > one more question.
> > when you define a trigger, as far as I understand, you have to operate
 on
> > the table itself (please correct if i'm wrong).
> > that makes a trigger a static rule associated with a table.
> > how if I want that trigger to be configurable?
> > for instance, I set my trigger to fire whenever the field salary gets an
> > increase of += 20%. after some time i want to change that value to 15%
> > without operating directly on the db.
> > Can I do that?
> > if so, how?
>
> No idea. How should the trigger "know" at what value it has to fire
> when you don't want to touch the database?
> The only suggestion I have is to enter the value in a parameter table
> and let the trigger query that table. But that will definitly cost
> performance.
>
> Regards,
>
> Knut

Put it as a constant in a package specification. Of course if the constant changes the trigger will need to be recompiled.

Hth,

Sybrand Bakker, Oracle DBA Received on Wed May 16 2001 - 13:09:13 CDT