Ask a Question
Report a Bug
This page in other versions:
This document in other formats:
Use the Domain Trigger dialog to define an event trigger. Unlike regular triggers, which are attached to a single table and capture only DML events, event triggers are global to a particular database and are capable of capturing DDL events. Like regular triggers, event triggers can be written in any procedural language that includes event trigger support, or in C, but not in SQL.
The Domain Trigger dialog organizes the development of a event trigger through the following dialog tabs: General, Definition, and Security Labels. The SQL tab displays the SQL code generated by dialog selections.
Use the fields in the General tab to identify the event trigger:
Click the Definition tab to continue.
Use the fields in the Definition tab to define the event trigger:
Click the Security Labels tab to continue.
Use the Security tab to define security labels applied to the trigger. Click the Add icon (+) to add each security label.
Click the Add icon (+) to assign additional security labels; to discard a security label, click the trash icon to the left of the row and confirm deletion in the Delete Row popup.
Click the SQL tab to continue.
Your entries in the Domain Trigger dialog generate a generate a SQL command. Use the SQL tab for review; revisit or switch tabs to make any changes to the SQL command.
The following is an example of the sql command generated by user selections in the Domain Trigger dialog:
The command creates an event trigger named accounts that invokes the procedure named acct_due.