Why not simply a Before Delete trigger that copies the row about to be
deleted over to a duplicate table. This way you can know exactly what the
data was before it was deleted. Of course, if you only care about a
certain field or group of fields you can always just copy those fields
instead of all fields.

We need to be able to track what records have been deleted from a table.

Our current thinking is
1. A "before delete" trigger, that stores a unique ID of the all the data
in
the table.
2. A "after delete" trigger, which gets the records left in the table.
3. Subtract the two lists to find the records that have been deleted.

This appears to be cumbersome, is there anyway to do this with one trigger
?

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).
--

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).

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 Mar 19 2002 - 07:28:20 CST