Re: Are Triggers Really that Bad or ....???

From: Ronnie Yours <ronnie_yours_at_yahoo.com>
Date: Wed, 14 Aug 2002 15:35:53 -0400
Message-ID: <ajebj0$40o$1@nntp-m01.news.aol.com>

Hi,

Sorry for bringing up a dead post again.

Is there a way I can simplify coding triggers for this kind of requirement, where I dont have to create a trigger for each and every table. I cannot use the type method you specified because the tables have already been created a long time ago and applications are accessing them.

Please Suggest

Ronnie

"David Fowler" <dbf57_at_earthlink.net> wrote in message news:pv309.6805$Ky3.394851_at_newsread2.prod.itd.earthlink.net...
> To avoid coding it over and over. create a oracle type with these columns
> and put it in the tables. Create a package with procedure/function handle
> insert /update.
> Call the package from the insert,update trigger. passing the type. Code is
> centrally controlled within the package the oracle type is all the tables.
>
> just a little object orientation.
>
> Dave Fowler
>
>
>
Received on Wed Aug 14 2002 - 14:35:53 CDT