Re: DB Triggers vs Stored Procedures

In a nutshell, it is better to put your code in a stored procedure outside of the trigger.

Why? Modular code is easier to reuse. You can't reuse code blocks that are in a trigger. There are other reasons, but this is the biggy IMO.

As Ferenc recommended, get the Feurstein book.

Jared

On Sunday 12 January 2003 22:03, Sathyanaryanan_K/VGIL_at_vguard.satyam.net.in wrote:
> Hi All
> I would like to know the difference between using the Stored procedures in
> DB Triggers and writing the code directly in the DB Trigger. Which would be
> better to use and what r the advantages.
> Rgds
> Sathya

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jared Still
  INET: jkstill_at_cybcon.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
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).