Well, despite the harsh words Sybrand used, his point holds up - approach
you suggested is incorrect. a) applies for sure if you use EXECUTE IMMEDIATE
and can be slightly reduced (but not totally avoided) with DBMS_SQL and
cursor caching; and b) is true unless you call the procedure in an AFTER INSERT
OR UPDATE trigger (and the question was about BEFORE triggers.)
Corrections and additions welcome.
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Rauf Sarwar" <rs_arwar_at_hotmail.com> wrote in message
news:92eeeff0.0207181954.1d8f6fc0_at_posting.google.com...
> > This code will result in
> >
> > a) Excessive parsing
> > b) in mutating table errors
> >
> > But then it might be possible to run it as a background job.
> >
> > Your advice above is absolute and utter crap.
> > Try to *learn* Oracle.
> >
> > Regards
> >
> >
> >
> > Sybrand Bakker, Senior Oracle DBA
> >
> > To reply remove -verwijderdit from my e-mail address
>
>
>
> Hmmm...relax Sybrand. You need to keep your prozac handy before you
> post or else you might give solutions like,
>
> > Don't use windows
> > Don't have power surges etc etc etc.
>
> It is not my job to judge how bad or good someone's database design
> is. Their database architect should have thought these things through
> at design time before slapping bunch of triggers on every table.
> Person wanted to know,
>
> > Finally, my problem is that I do not know how to send the table (as an
> > object) to procedure!
>
> and my solution to that is to use dynamic plsql. If you have a better
> or another solution, then post it, else go see a shrink before your
> *little bubble* bursts up with a whimper.
>
> //Rauf Sarwar
Received on Fri Jul 19 2002 - 07:07:03 CDT
