Re: And another one about PL/SQL

"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message news:<3d122e67$0$230$cc9e4d1f_at_news.dial.pipex.com>...
> "Rauf Sarwar" <rsarwar_at_ifsna.com> wrote in message
> news:c2d690f2.0206200935.71963dc7_at_posting.google.com...
> > "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message
> news:<3d1197f1$0$236$ed9e5944_at_reading.news.pipex.net>...
> > > "Rauf Sarwar" <rsarwar_at_ifsna.com> wrote in message
> > > news:c2d690f2.0206191405.b92b46_at_posting.google.com...
> > > > Since triggers are known to be very unstable, I would highly recommend
> > > > using PACKAGES.
> > >
> > > care to justify that comment. I certainly don't consider triggers (or
> > > standalone proceudres for that matter) unstable. Howard is using IMO
> exactly
> > > the right tool for the job.
> > >
> > >
> > > --
> > > Niall Litchfield
> > > Oracle DBA
> > > Audit Commission UK
> > > *****************************************
> > > Please include version and platform
> > > and SQL where applicable
> > > It makes life easier and increases the
> > > likelihood of a good answer
> > >
> > > ******************************************
> >
> >
> > I have recieved some emails beside replies to my post about "Triggers
> > being unstable". I think I should have elaborated my dislike for
> > triggers which I also think are unstable...__BUT__ I do want to put a
> > disclaimer that when I say unstable, I __DO NOT__ mean that triggers
> > will crash your database or application. They are unstable (In my
> > view) when you have a big database (2000 + tables) and you tightly
> > want to enforce business rules, Data integrity and at the same time
> > tightly control access to base tables. It all depends how one wants to
> > build the database and what kind of business rules will be applied. In
> > some instances triggers will work better and in some instances,
> > packages will work better...(There I said it!!!).
>
> Thanks for the whole post (some of which I have snipped). What you have
> posted I don't (disclaimer -after 2 minutes thought only - /disclaimer)
> disagree with. I don't think it supports your original statement "triggers
> are known to be unstable" but I do think it supports the statement "triggers
> are not always the best choice to enforce business rules". Unstable shouts
> database crash, application crash, server crash etc. To me anyway.

Niall,

Thanks for your input. I know "Unstable" lights up red lights everywhere. More appropriate would have been "Triggers are known to be a very bad choice" in some instances (In my case...I discard them 95% of the time). Received on Fri Jun 21 2002 - 09:43:03 CDT