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

"Hugues Parvillers" <Hugues.Parvillers_at_AgdF.com> wrote in message news:3D3F14A8.CF9B219_at_AgdF.com...
> Ten years ago, would have been bad idea to use triggers
> Five years ago, could have been discussed also.
> But now !!!
> Should I say that for my self I use trigger to full backup previous state
of
> rows under a xml serialisation of the previous state of any row :-) . Via
> trigger.
>
> HP
>
> Ronnie Yours a écrit :
>
> > Hi,
> >
> > I am facing a wierd situation here.
> >
> > We have a database with around 150-200 Tables and growing . Each Table
has
> > 4 columns in additional to the ones for the application, namely
> > created_by, created_date,updated_by and updated_date.
> > Now when writing the application code the developers were supposed to
take
> > care of the values in these fields. For example when a record is
> > added/inserted the created_by and created_date fields are populated and
when
> > the records are updated the updated_by and updated_dates are
> > populated/updated.
> > But the issue is the developeres did not take care of this issue and one
of
> > the senior developers is suggesting that lets create triggers to
implement
> > this functionality.
> >
> > My suggestion was and is that lets change the code to take care of this
but
> > he doesnt agree. He says it will take more time to do that.
> >
> > Now I am in a dilemma.
> >
> > If we implement triggers how will they affect the prformance.
> > If I should not implement triggers then how should I go about handling
this
> > situation and explain the same to my manager.
> >
> > Please Suggest
> >
> > Thanks
> > Ronnie Yours

I have a very strong opinion here; sorry to any offended... IMHO, these kinds of things should be coded in the database from the outset, and there is no justifiable alternative.

Regards,
Paul Received on Wed Jul 24 2002 - 18:13:20 CDT