You could use VPD (virtual private database, AKA fine-grained
access control AKA row-level security) to control exactly which
rows a given user can delete based on a function using the
business rule which determines which rows they are authorized to
delete. This works from 8i onward, but there
It is meant to be a 'selective' deletion i.e. some rows should be allowed to
delete where as others shouldn't be. Thanks for your replies.
Regards,
Charu.
-Original Message-
Sent: Monday, October 14, 2002 8:30 PM
To: Multiple recipients of list ORACLE-L
Why not just remove delete author
Why not just remove delete authority from anyone not authorized to delete
from it ??
-Original Message-
Sent: Monday, October 14, 2002 2:34 PM
To: Multiple recipients of list ORACLE-L
CREATE OR REPLACE TRIGGER temp_trig BEFORE DELETE ON temp_tab FOR EACH ROW
BEGIN
RAISE_APPLICAT
CREATE OR REPLACE TRIGGER temp_trig BEFORE DELETE ON temp_tab FOR EACH ROW
BEGIN
RAISE_APPLICATION_ERROR(-2,'Do not delete ...');
END;
/
Bala.
-Original Message-
Sent: Monday, October 14, 2002 1:14 PM
To: Multiple recipients of list ORACLE-L
Dear Listers,
I hope you won't m
Here's one way:
drop table d;
create table d( x integer );
create or replace trigger d_nodelete_trg
before delete
on d
begin
raise_application_error(-2,'No Deletes Allowed!');
end;
/
show error trigger d_nodelete_trg
Jared
"Charu Joshi" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECT
Title: RE: Elementary question about triggers
Basics:
1. Delete trigger doesn't delete the row, the DELETE command does it.
2. DELETE command invokes the delete trigger (if the trigger conditions are met).
Solution:
1. Revoke delete priv so no deleted can take place.
2. Create a b
