Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: PL/SQL text within TRIGGERs

RE: PL/SQL text within TRIGGERs

From: <J.Velikanovs_at_alise.lv>
Date: Tue, 22 Jun 2004 13:04:11 +0300
Message-ID: <OF409C8F8C.65500AEA-ONC2256EBB.0036BCE3-C2256EBB.0037F763@alise.lv>


Good discussion, indeed!
Thank you Justin for pointing me ;)

Summary:
>> Triggers have an entirely different history then stored procedures so
the
>> reasoning is probably legacy in nature. Prior to 7.3, they were not
stored
>> compiled - they were just stored as "text". I have a feeling that deep
down
>> they are still very much like an anonymous plsql block as they used to
be --
>> just stored compiled.

Any SQL within TRIGGER will be parsed (probably soft parsed) for each SQL call. If we write SQL within procedure and call this procedure from the trigger SQL can be cashed and parsing step will be skipped.

Thank you again,
It is right that I looking for,
Jurijs
9268222



http://otn.oracle.com/ocm/jvelikanovs.html

"Justin Cave" <justin_at_askddbc.com>
Sent by: oracle-l-bounce_at_freelists.org
22.06.2004 12:47
Please respond to oracle-l  

        To:     <oracle-l_at_freelists.org>
        cc: 
        Subject:        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



Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------




----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------



----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Received on Tue Jun 22 2004 - 05:08:18 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US