I read it somewhere that stored procs are precompiled which means these are
faster compared to triggers ( these are compiled at run time ) , also if you
have stored proc you can reuse then but u cant reuse triggers .
-Bp
- Original Message -----
To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com>
Sent: Tuesday, June 11, 2002 8:38 AM
> Hi all,
>
> Does anyone have any recommendations for db trigger size?
>
> Some developers here write triggers that have 400-700 lines in them. I am
> pushing them to write a package and call that package from within the
> trigger. But to put this argument forward, I need to give some good
> reasoning and that's why I am looking for some recommendations.
>
> Some of these triggers are on tables that are most active in the database
> (i.e. DML ALL the time) and none of the triggers are pinned.
>
> Thanks in advance
> Raj
> ______________________________________________________
> Rajendra Jamadagni MIS, ESPN Inc.
> Rajendra dot Jamadagni at ESPN dot com
> Any opinion expressed here is personal and doesn't reflect that of ESPN
Inc.
>
> QOTD: Any clod can have facts, but having an opinion is an art!
>
>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: BigP
INET: big_planet_2000_at_hotmail.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Tue Jun 11 2002 - 21:43:23 CDT
