| Name | Meta_Trigger |
|---|---|
| Entity Type | External |
| Description | A database trigger, i.e., a programming construct executed when a database event occurs, such as an Insert, Update, or Delete. |
| Submodel | Meta |
| Entity Scope | Meta |
| Primary Key | Name , Scope_Name , Sub_Type |
| Natural Key | Name , Scope_Name , Sub_Type |
| Generalizations | Meta_Program_Text |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Entity_Name | STRING64 | NA |
The name of the entity with which this trigger is associated. | No |
VARCHAR2(64) |
| Name | STRING64 | NA |
The name of the program module. | Yes |
VARCHAR2(64) |
| Program_Text | CLOB | NA |
The text of the program module expressed in some programming language such as PL/SQL or TSQL. | No |
CLOB |
| Public_Flag | boolean | NA |
A flag that indicates if the object is public, i.e., a user-defined custom object (value = 1 (True)); or is defined and owned by Seabed (value = 0 (False)). The default value is 0 (False). | No 0 |
NUMBER(1) |
| Scope_Name | CODE | NA |
The name of the scope of the program module. The scope indicates the area of influence or coverage within which this entity operates. Examples of possible values for scope are: System - this entity lives at the system level, an example is a user: Data Dictionary - this entity lives at the data dictionary level, an example is a meta entity: Project - the scope of this entity is a single project - an example is a well or borehole: and Reference - this entity exists within the reference scope - an example is a well status lookup table. | Yes |
VARCHAR2(64) |
| Sub_Type | CODE | NA |
The sub type of program module. The valid values are: Trigger, View, Procedure, ObjectView, SpatialView, and Function. | Yes |
VARCHAR2(64) |
| Trigger_Event | CODE | NA |
The event that causes the database trigger to execute (fire). Examples include Before Insert, Before Update, After Insert, and After Update. | No |
VARCHAR2(64) |