Oracle 视图 ALL_TRIGGERS 官方解释,作用,如何使用详细说明
本站中文解释
Oracle视图ALL_TRIGGERS,索引了当前用户可以访问的所有触发器(trigger)信息。
ALL_TRIGGERS视图中存储的视图元数据包括:触发器的名称、触发器的状态、触发时间、表或视图的名称、触发代码、触发器的类型等。
使用ALL_TRIGGERS视图可以快速访问当前用户可用的触发器信息,常见的使用是查看已经存在的触发器,查看触发器是否已经启用,或者检查触发器触发时间是否为正确的等,也可以使用ALL_TRIGGERS视图来生成或克隆触发器模板代码。
使用ALL_TRIGGERS:
SELECT * FROM ALL_TRIGGERS; –查询当前用户可以访问的触发器信息
官方英文解释
ALL_TRIGGERS
describes the triggers on tables accessible to the current user.
If the user has the CREATE ANY TRIGGER
privilege, then this view describes all triggers in the database.
Related Views
-
DBA_TRIGGERS
describes all triggers in the database. -
USER_TRIGGERS
describes the triggers owned by the current user. This view does not display theOWNER
column.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
Owner of the trigger |
|
|
|
Name of the trigger |
|
|
|
When the trigger fires:
|
|
|
|
DML, DDL, or database event that fires the trigger See Also: Oracle Database PL/SQL |
|
|
|
Owner of the table on which the trigger is defined |
|
|
|
Base object on which the trigger is defined:
|
|
|
|
If the base object type of the trigger is |
|
|
|
Name of the nested table column (if a nested table trigger), else NULL |
|
|
|
Names used for referencing |
|
|
|
Must evaluate to |
|
|
|
Indicates whether the trigger is enabled ( |
|
|
|
Trigger description; useful for re-creating a trigger creation statement |
|
|
|
Action type of the trigger body:
|
|
|
|
Statements executed by the trigger when it fires |
|
|
|
Type of crossedition trigger:
|
|
|
|
Indicates whether the trigger has a |
|
|
|
Indicates whether the trigger has a |
|
|
|
Indicates whether the trigger has an |
|
|
|
Indicates whether the trigger has an |
|
|
|
Indicates whether the trigger has an |
|
|
|
Indicates whether the trigger will fire only for user processes making changes ( |
|
|
|
Indicates whether the trigger will only fire for a Replication Apply or SQL Apply process ( See Also: the |
See Also:
-
“DBA_TRIGGERS”
-
“USER_TRIGGERS”
-
Oracle Database PL/SQL
Packages and Types Reference for more information about theDBMS_DDL.SET_TRIGGER_FIRING_PROPERTY
procedure