| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: PL/SQL text within TRIGGERs
This is generally still a good recommendation. Tom Kyte has a discussion of
this here:
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:750770687
5149
The Cliff Notes version is that trigger code has to be (soft) parsed on each execution, so you'll get more scalability embedding the code in stored procedures.
Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of J.Velikanovs_at_alise.lv
Sent: Tuesday, June 22, 2004 3:46 AM
To: oracle-l_at_freelists.org
Subject: PL/SQL text within TRIGGERs
Hi gurus!
At the beginning of my career ~5-6 years ago some one, told me that write
PL/SQL text within TRIGGER body is not good idea, because trigger text
compiling by Oracle at each trigger call. And it is better idea, to call
from trigger just procedure there we implement all the code. At the moment I
don't remember who told me about this issue, I even don't know was it at
Oracle course or at other event time.
Is this recommendation is myth or it still true for Oracle environment. Can anybody comment on it?
Thank you in advance,
Jurijs
 |
 |