Database Triggers: - A set of pl/sql statements stored permenantly in database and "automatically" activated when ever an event raising

statement ( DML ) is executed. - They are stored in "User_Triggers" system table. - They r used to impose Business rules / user Table columns. - They r also activated when Tables are or by other application s/w tools. - They provide high security on tables. Trigger Parts: 4 Parts 1. Triggering Event : Indicates when to activate the trigger . -- insert / update / delete After -- insert / update / delete 2. Trigger Types: 2 Types i) Row Triggers : Activates the trigger for every statement. update emp set sal = sal + 2000; ii) Statement Triggers: Activates the trigger for atement ( Default Type ) 3. Trigger Restriction: Used to stop the activation of trigger based on on is True trigger is active. 4. Trigger Body: A set of pl/sql statements Syntax: Create or replace Trigger < Trigger name > before/after insert or update or delete -- 1 [ of <columns> ] on < Table name > [ for each row -- 2 when (< condition >) -- 3 * if condition is True trigger is executed declare < variable declaration >; ] begin < exec stmts >; [ exception <exec stmts >; ] end; --------------------------------------------------------------create table stu_info (roll number(3), sname varchar2(20), course varchar2(20), fee number(5)); insert into stu_info racle',2500); * Trigger converts student name to upper case create or replace Trigger up_con before insert on stu_info for each row values(100,'srinivas','o automatically. Before defined restrictions on manipulated by other users

row manipulated by DML

only once for 1 DML st

condition. If conditi

begin :new.sname := upper(:new.sname); end; insert into stu_info 2500); values(101,'sriram','oracle',

>select * from stu_info; 101 SRIRAM oracle 2500 --------------------------------------------------------------New & Old ( Pseudo Columns ): ------------------------------------Used to retrieve data from DML stmt temporary buffer into Trigger Body. * valid with "ROW" triggers only. NEW OLD INSERT UPDATE DELETE valid valid invalid invalid valid valid

* New supports with Insert and Update stmts . * Old supports with Update and Delete stmts . * They r refered with : (colon) to indicate as Bind variables. They r accessed from SQL buffer to Pl/sql block. --------------------------------------------------------------Triggering Events: Before insert Row, Before update Row, Before delete Row Before insert Stmt, Before update Stmt, Before delete Stmt After insert Row, After update Row, After delete Row After insert Stmt, After update Stmt, After delete Stmt 12 Events per Table are allowed. --------------------------------------------------------------* Modifying existing trigger create or replace Trigger up_con before insert on stu_info for each row begin if :new.course = 'oracle' and :new.fee = 2100 then :new.sname := upper(:new.sname); else :new.sname := lower(:new.sname); end if; end; insert into stu_info values(103,'sekhar','oracle' ,2100); insert into stu_info values(104,'SRINATH','oracle' ,1000); select * from stu_info; 103 SEKHAR oracle 2100 104 srinath oracle 1000 --------------------------------------------------------------* Trigger Checks for valid increment on employ salary : >create or replace trigger chk_incr before update of sal on emp for each row

begin if :new.sal <= :old.sal then raise_application_error(-20300,' Increment must lary '); end if; end;

be more than existing sa

>update emp set sal = sal - 3000 where empno = 7900; >update emp set sal = sal - sal *.35; -------------------------------------------------------------Note: Column Specification [ of sal ] is supported with UPDATE event only. Not valid with Insert and Delete Operations ( Row Level Operations ). Activates the Trigger only when that particular column is updated . * Raise_application_error(error no,error message); Built_in sub program stops the DML stmt execution and displays the error message. Error No Range : -20001 to -20999 Oracle Reserved Error Nos: -20000 to +20000 --------------------------------------------------------------* Trigger checks for null value in dept name. >create or replace trigger chk_null before insert or update of dname on dept for each row begin if :new.dname is null then raise_application_error(-20301, ' Department name cannot be blank '); end if; end; >insert into dept values(98,null,'Hyd'); >update dept set dname = null where deptno = 30; --------------------------------------------------------------Note: Constraint Vs Trigger Constraints will check for existing rows also Triggers will not check for existing rows Constraints provide standard error messages Triggers provide user friendly error messages Constraints provides pre-defined rules on table Triggers provides user-defined rules on table columns. columns.

* If constraint & Trigger are defined on table at a time only Trigger wil l be activated. ( If both r checking for same condition ) --------------------------------------------------------------> Create table job_pays ( job varchar2(20), Losal number(10), hisal number(10)); insert into job_pays values ('CLERK' , 3000 , 10000); insert into job_pays values ('SALESMAN' , 5000 , 15000); insert into job_pays values

('MANAGER' , 8000 , 20000); insert into job_pays values ('ANALYST' , 10000 , 30000); insert into job_pays values ('EXECUTIVE' , 10000 , 25000); * Trigger Checks for valid salary according to the Job. create or replace trigger chk_sal before insert on emp for each row -- if condition is True trigger will be executed -- if condition is False trigger will NOT execute when (new.job NOT IN ('PRESIDENT','DIRECTOR')) declare minpay number(10); maxpay number(10); begin select Losal,hisal into minpay,maxpay from job_pays where job = :n ew.job; if :new.sal < minpay or :new.sal > maxpay then raise_application_error(-20200,' Salary must be between '||minpay||' and '||maxpay|| ' for Job '||:new.job); end if; exception when no_data_found then raise_application_error(-20201,' No such job exists '||:new.job); end; Insert into EMP(empno,ename,job,sal,deptno) values (&1,'&2','&3',&4,&5); --------------------------------------------------------------* Trigger adds the increment amount automatically to Employ salary. ( Using IMPLICIT Cursor ) create or replace trigger add_incr before insert on incr for each row begin update emp set sal = sal + :new.amt where empno = :new.empno; -- Using implicit cursor if sql%notfound then raise_application_error(-20111,' No such employ |:new.empno); end if; end;

exists with employ code '|

create table incr(empno number(4), amt number(10)); select empno,ename,sal from emp where empno = 7900; 7900 JAMES 8000 insert into incr values(7900,4000); select empno,ename,sal from emp where empno = 7900; 7900 JAMES 12000 insert into incr values(790,2000); --------------------------------------------------------------Student Fee_instalments

--------roll - 101 name - RAM 101 course - Oracle 101 fee - 5000 101 ( 2000 + 2000 + 1000 )

-------------------roll prev_fee curr_fee DOP 0 1000 --1000 2000 --3000 2000 ---

create table student (roll number(3), sname varchar2(20), course varchar2(20), fee number(5)); create table fee_instalments (roll number(3), prev_fee number(5), curr_fee number(5), dop date); * Trigger adds the fee instalment amount ee_instalments table . create or replace trigger add_fee before insert or update or delete on student for each row begin if inserting then insert into fee_instalments values (:new.roll, 0, :new.fee, sysdate); elsif updating then insert into fee_instalments values (:old.roll, :old.fee, :new.fee - :old.fee, sysdate); elsif deleting then delete from fee_instalments where roll = :old.roll; end if; end; insert into student ); update student set fee = fee + 2000 where roll = 101; update student set fee = fee + 2000 where roll = 101; select * from fee_instalments; values(101,'RAM','oracle',1000 automatically into f

* Keywords: inserting, updating, deleting - Represents insert, update and delete operations - Used to identify the operation performed by user - Valid in Triggers only --------------------------------------------------------------Transaction -- Table -------------Accno tran_type amt 101 D 5000 102 D 7500 103 D 1000 104 W 1000 105 W 9000 103 D 9000 * Statement Level Trigger: * Triggers Locks the Transaction table for update ( Only insert allowed ) and delete operations.

create or replace trigger lock_trans before update or delete on Transaction begin raise_application_error(-20555, ' Invalid operation on Transaction Table '); end; delete from transaction; update transaction set amt = amt + 1000; --------------------------------------------------------------Disabling Triggers: >Alter table transaction disable all triggers; >Alter table bankmaster disable all triggers; Enabling Triggers: >Alter table transaction enable all triggers; >Alter table bankmaster enable all triggers; Removing Triggers: Drop trigger < Trigger name >; >Drop trigger CHK_SAL; Checking for Existing Triggers: >desc User_triggers >select trigger_name , triggering_event from user_triggers where table_name = 'EMP'; >select * from user_triggers where trigger_name = 'CHK_SAL'; >select text from USER_SOURCE where name = 'CHK_SAL'; >desc user_source * User_source -- system table holds the details of Triggers .( body ) --------------------------------------------------------------* Statement Level Trigger: * Trigger Locks the table for DML operations to provide security: * Trigger checks for i> Valid Timings ii> Weekends iii> Public Holidays create or replace trigger security_chk before insert or update or delete on bankmaster declare a number; begin -- check for valid Timings ( 10 am to 6 pm ) if to_char(sysdate,'hh24') not in hen raise_application_error(-20111,' No operations s '); end if; -- check for weekends if to_char(sysdate,'dy') in ('sat','sun') then raise_application_error(-20112,' No operations end if; -- check for Public Holidays select count(*) into a from holiday where to_date(hdate) = to_date(sysdate); if a > 0 then raise_application_error(-20113,' No operations

(10,11,12,13,14,15,16,17) t allowed - Invalid Timing

allowed - Weekends ');

allowed - Public Holiday

'); end if; end; Holiday -- table -------hdate --'19-mar-11' '01-may-11' description --- 'Holi' 'May Day' --------------------------------------------------------------* Trigger updates Transactions automatically to Master table. Bankmaster ------------accno name acc_type curr_bal insert into bankmaster create or replace trigger add_deposit After insert on transaction for each row begin if :new.tran_type = 'D' then update bankmaster set curr_bal = curr_bal + ew.accno; end if; end; Transaction -------------accno tran_type tran_date amt values(101,'RAM','S',20000);

:new.amt where accno = :n

insert into transaction values(101,'D',sysdate,10000); insert into transaction values(101,'D',sysdate,30000); select * from bankmaster; 101 RAM S 60000 --------------------------------------------------------------Instead of Triggers: [ 8i ] - Triggers supported only on "views" * - Used to perform DML operations on "Join views" * Instead of --- insert , update , delete Ex: 1 >create view v1 as select * from emp; >create trigger t1 instead of delete on v1 for each row begin dbms_output.put_line(' Record Removed '); end; > delete from v1 where empno = 7900; > select * from v1 where empno = 7900; --------------------------------------------------------------** Manipulating Join views thru Instead of Triggers Ex: 2 >create view edept as select empno, ename, sal, job, emp.deptno, dept.dep tno dno, dname, loc from emp, dept where emp.deptno = dept.deptno; > insert into edept 050,'VIJAY',20000,'MANAGER', 80,80,'TECHNICAL','HITECH'); values(1 --- error

>create trigger Trig2 instead of insert on edept for each row begin insert into dept new.dno,:new.dname,:new.loc); insert into emp(empno,ename,sal,job,deptno) ame,:new.sal, :new.job, :new.deptno); end; /

values(: values(:new.empno,:new.en

>insert into edept values (......); --- repeat step 2 >select * from edept; --------------------------------------------------------------Ex : 3 >delete from edept where deptno = 80; ( Removes data from emp table only - key preserved table [8.0] ) * Trigger Removes records from 2 tables create or replace trigger Trig3 instead of delete on edept for each row begin delete from emp where deptno = :old.deptno; delete from dept where deptno = :old.deptno; end; delete from edept where deptno = 80; ( Removes so ) data from emp , dept table al

Note : Supports to manipulate Multiple tables thru one DML stmt thru Join Views. --------------------------------------------------------------Invalid Triggers : 1. >create table temp1(c1 number(3), c2 varchar2(10)); 2. >create trigger trig11 before insert on temp1 for each row begin insert into temp1 values(102,'SIVA'); end; / 3. >insert into temp1 values(101,'RAM'); Error: It leads to an infinite loop --------------------------------------------------------------- >create trigger trig12 before insert on temp1 for each row begin update temp1 set c2 = 'HARI'; end; >insert into temp1 values (102,'RAVI'); It will not perform update in Trigger body becoz 2 DML operations cannot be performed on table at once. It leads to a " Trigger Mutuation " error while working with other s/w tools. ** If Trigger applied on Table1

( before insert on Table1 ) performing any other DML on same table ( Table 1) in trigger body causes Mutuating Error . --------------------------------------------------------------- Note: ( commit , rollback ) ** TCL commands are not allowed in Triggers. Becoz Trigger will be executed while performing DML stmt but TCL has to be given after DML stmt execution. --------------------------------------------------------------Advantage of Database Triggers: - Automatic execution of code based on event . - Used to impose user defined restrictions on Tables . - Provides Security on Tables while Manipulating data from any where . ---------------------------------------------------------------