[EMAIL PROTECTED] wrote:
Hi,
I know for example, I can access :new values and :old values. I also thought
that I could access the TYPE of ddl that caused the trigger to fire and I am
wondering if I have access to the sql that caused the trigger to fire.
I am looking in the
Hi,
This should work. But I took the messier approach (I have 8i) and created before
insert/update/delete triggers on the suspect tables. I am testing in a schema on an
instance where there is alot of activity on the other schemas.
BUT, I will look into further for future use.
Thanks,
Hi,
I know for example, I can access :new values and :old values. I also thought that
I could access the TYPE of ddl that caused the trigger to fire and I am wondering if I
have access to the sql that caused the trigger to fire.
I am looking in the application development PL/SQL
by type of ddl do you mean insert/update/delete?
if so, you can code the trigger as on insert on update etc (or a
combination of those values) and you can test for which of them it is
(if you have coded the combination)
as far as I know, you do not have access to the sql itself.
--- [EMAIL
.
still working on it.
Thanks,
Hannah
-Original Message-
From: [EMAIL PROTECTED]@SUNGARD On Behalf Of Rachel Carmichael
[EMAIL PROTECTED]
Sent: Tuesday, June 25, 2002 5:11 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: What Attributes
Title: RE: What Attributes are available to a Trigger
You can do something like this:
create or replace trigger LogChanges
before insert or delete or update on table1
for each row
declare
v_changetype char(1);
begin
if inserting then
v_changetype := 'I';
elseif updating
