Re: OLD and NEW in DB TRIGGERS

In Article<4kls7s$7va_at_dfw-ixnews7.ix.netcom.com>, <merrittk_at_ix.netcom.com> write:
> Path: news.NetVision.net.il!psinntp!psinntp!psinntp!howland.reston.ans.net!ix.netcom.com!news
> From: merrittk_at_ix.netcom.com(Kevin Merritt )
> Newsgroups: comp.databases.oracle
> Subject: OLD and NEW in DB TRIGGERS
> Date: 12 Apr 1996 15:18:20 GMT
> Organization: Netcom
> Lines: 19
> Message-ID: <4kls7s$7va_at_dfw-ixnews7.ix.netcom.com>
> NNTP-Posting-Host: irv-ca7-03.ix.netcom.com
> X-NETCOM-Date: Fri Apr 12 10:18:20 AM CDT 1996
>
> There's a lot of "press" advocating converting DB triggers to stored
> procedures when the trigger exceeds 60 lines of code. This is all well
> and good, but how can I have access to the correlation rows OLD and NEW
> in my stored procedure? I want to see the before and after values from
> inside my stored procedure.
>
> For example, in my DB trigger I want to call my stored procedure
>
> CREATE TRIGGER xxx
> AFTER UPDATE
> ON TABLE_YYY
> REFERENCING OLD AS OLD NEW AS NEW
> FOR EACH ROW
> DECLARE
> BEGIN
> XXX_TRG_STORPROC(old, new);
> END;
>
> Any bright ideas would be appreciated.

no bright ideas for you, just pass then as parameters (column by column) Received on Mon Apr 15 1996 - 00:00:00 CEST