Kbase P33396: How to disable schema triggers using 4GL/ABL
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/14/2008 |
|
Status: Verified
GOAL:
How to disable schema triggers using 4GL/ABL
GOAL:
Example using the DISABLE TRIGGERS statement
GOAL:
Can a database trigger be disabled via Data Dictionary?
FACT(s) (Environment):
All Supported Operating Systems
Progress 7.x
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
The following is extracted from the documentation.
DISABLE TRIGGERS Statement
Disables database triggers before you perform a dump or load procedure. You must have CAN-DUMP and CAN-LOAD permissions on the table for which you want to disable the triggers.
SYNTAX:
DISABLE TRIGGERS FOR { DUMP | LOAD } OF table-name [ ALLOW-REPLICATION ]
DUMP
Disabling triggers for DUMP disables the trigger associated with the FIND event for the named table.
LOAD
Disabling triggers for LOAD disables all triggers associated with the CREATE, WRITE, and ASSIGN events for the named table.
table-name
The name of the table for which you want to disable the triggers. You can name only one table.
ALLOW-REPLICATION
Tells DISABLE TRIGGERS to disable only CREATE, DELETE, ASSIGN, and WRITE triggers, and not REPLICATION-CREATE, REPLICATION-DELETE, and REPLICATION-WRITE triggers.
For more information on database replication, see the reference entry for the
RAW-TRANSFER Statement in this book, and the Progress Database Administration
Guide and Reference.
Note that -
- You could remove the trigger procedure from the schema via the Data Dictionary, but the is no option in Data Dictionary to disable the trigger.
- Triggers disabled with the DISABLE TRIGGERS statement remain disabled for the duration of the procedure in which you issued the statement and any subprocedures.
- The Progress Data Dictionary automatically disables the appropriate triggers during data dump and load operations.