Deleting with Instead Trigger in Oracle 8i

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Thu, 17 Apr 2003 08:05:42 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA70390FD00@lnewton.leeds.lfs.co.uk>

Morning Paul,

yep - that's how it works.

Now, how do we developers/dbas do it ?
Why we always use :new in a delete trigger and get confused when it doesn't delete, but tells us that it did :o)

I knew the answer myself because I've been down that road a couple of times - one day I'll learn !

Cheers,
Norm.

Norman Dunbar
Database/Unix administrator
Lynx Financial Systems Ltd.
mailto:Norman.Dunbar_at_LFS.co.uk

Tel: 0113 289 6265
Fax: 0113 289 3146
URL: http://www.Lynx-FS.com
-------------------------------------

-----Original Message-----
From: Paul Brewer [mailto:paul_at_paul.brewers.org.uk] Posted At: Wednesday, April 16, 2003 10:35 PM Posted To: server
Conversation: Deleting with Instead Trigger in Oracle 8i Subject: Re: Deleting with Instead Trigger in Oracle 8i

I may well have missed something, but all of this seems reasonable enough to
me.
From an empirical point of view, one would tend to assume that on insert,
:old would be null, and :new contains the inserted values. On update,
:old

and :new would reflect the obvious, and on delete :old would be the 'before
image', whereas :new would be null.

Isn't that how it works? Received on Thu Apr 17 2003 - 02:05:42 CDT