Oracle Trigger :Before,after,each row and table level triggers ORA-04082 ORA-04084
2007-07-28 19:54
656 查看
Before, after, each row and table level triggers [Oracle]
The goal of this page is to demonstrate the most important differences between before and after triggers as well as the differences between for each row and table level triggers.Before / for each row trigger
A before trigger is called before because it fires beforecreate table t_update_before_each_row ( txt varchar2(10) ); create table log ( txt varchar2(20) ); create trigger update_before_each_row before update on t_update_before_each_row for each row begin :new.txt := upper(:new.txt); insert into log values ('old: ' || :old.txt); insert into log values ('new: ' || :new.txt); end update_before_each_row; /
insert into t_update_before_each_row values('one'); insert into t_update_before_each_row values('two'); insert into t_update_before_each_row values('three'); insert into t_update_before_each_row values('four');
Updating (that is: concatenating the value with itself) the rows containing two and three:
update t_update_before_each_row set txt = txt || txt where substr(txt,1,1) = 't';
select * from t_update_before_each_row;
As can be seen by the output of the select statement, the trigger changed the values of the new values; they're in uppercase now:
one TWOTWO THREETHREE four
The log displays the old and new values:
select * from log;
old: two new: TWOTWO old: three new: THREETHREE
Cleaning up:
drop table t_update_before_each_row; drop table log;
After / for each row trigger
In contrast to a before trigger, an after trigger does not allow to change:new.field_namebecause the value is, when the trigger fires, already written to the table.
If one tries to assign a value to
:new.field_name, Oracle throws an ORA-04084: cannot change NEW values for this trigger type.
create table t_update_after_each_row ( txt varchar2(10) ); create table log ( txt varchar2(20) ); create trigger update_after_each_row after update on t_update_after_each_row for each row begin -- :new.txt := upper(:old.txt); -- ORA-04084: cannot change NEW values for this trigger type insert into log values ('old: ' || :old.txt); insert into log values ('new: ' || :new.txt); end update_after_each_row; /
insert into t_update_after_each_row values('one'); insert into t_update_after_each_row values('two'); insert into t_update_after_each_row values('three'); insert into t_update_after_each_row values('four');
update t_update_after_each_row set txt = txt || txt where substr(txt,1,1) = 't';
select * from t_update_after_each_row;
one twotwo threethree four
select * from log;
As the log table shows, it is possible to use
:newand
:oldalthough it's not possible to assign something to
:new.
old: two new: twotwo old: three new: threethree
Cleaning up:
drop table t_update_after_each_row; drop table log;
Table level trigger
A table level trigger is a trigger that doesn't fire for each row to be changed. Accordingly, it lacks thefor each row. Consequently, both, the
:newand
:oldare not permitted in the trigger's PL/SQL block, otherwise, an ORA-04082: NEW or OLD references not allowed in table level triggers is thrown.
create table t_update_before ( txt varchar2(10) ); create table log ( txt varchar2(20) ); create trigger update_before before update on t_update_before begin -- :new.txt := upper(:old.txt); -- ORA-04082 insert into log values ('update trigger'); end update_before; /
insert into t_update_before values('one'); insert into t_update_before values('two'); insert into t_update_before values('three'); insert into t_update_before values('four');
update t_update_before set txt = txt || txt where substr(txt,1,1) = 't';
select * from t_update_before;
one twotwo threethree four
select * from log;
Although two rows were updated, only one record is found in the log table:
select * from log;
update trigger
An update statement that doesn't update any row:
update t_update_before set txt = txt || txt where txt = 'no update';
Still, the trigger fires...
select * from log;
... which results in another row found in the log table:
update triggerupdate trigger
Cleaning up:
drop table t_update_before; drop table log;
Order of execution
Oracle allows to create multiple triggers on the same table. The order of the execution of these triggers is undeterministic (or random, if you want this word) except that all before triggers fire before the after triggers.相关文章推荐
- Before, after, each row and table level triggers [Oracle]
- Oracle —— before row trigger OR after row trigger
- 【Oracle问题集5】ORA-55622: DML, ALTER and CREATE UNIQUE INDEX operations are not allowed on table
- Oracle-Trigger-Insert tableA and tableB
- ORA-04098: trigger 'SYS.GGS_DDL_TRIGGER_BEFORE' is invalid and failed re-validation
- oracle自增auto_increment与oracle 创建触发器是非法的 ORA-04098: trigger 'USER_TRIGGER'is invalid and failed re-v
- oracle trigger中的before和after
- [Bug]ArcSDE分区表报:ORA-14301: table-level attributes must be specified before partition-level attribute
- oracle常用的复合数据类型 : BULK COLLECT和is table of table_name%rowtype index by
- Ch4.4: array to Balanced tree and print each level
- Oracle 10g 异常:ORA-01950: no privileges on Tablespace
- After delete Trigger throw error:The row value(s) updated or deleted either do not make the row unique or they alter multiple rows (2 rows).
- oracle日期时间段查询遇到问题to_date ora-01847 day of month must be between 1 and last day of month
- CRT code before and after main
- Animation.setFillAfter and Animation.setFillBefore的作用
- 14.64.3 行过滤及排序键 Table row filer and sort key
- [ORACLE错误]ORA-00054:resource busy and acquire with nowait specified解决方法
- Oracle Study Note : Tablespace and Data Files
- There will be decreasing performance of oracle by delete whole table and then insert ...
- ORA-00604: error occurred at recursive SQL level 1 ORA-00054: resource busy and acquire with NOWAIT