DISABLE TRIGGERS statement
- Last Updated: October 16, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
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
|
- 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, DELETE, REPLICATION-CREATE, REPLICATION-WRITE, REPLICATION-DELETE, 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, ASSIGN, and WRITE
triggers, and not REPLICATION-CREATE, REPLICATION-DELETE, and REPLICATION-WRITE
triggers. The DELETE trigger is not disabled.
For more information on database replication, see the reference entry for the RAW-TRANSFER statement, and Manage the OpenEdge Database.
Example
The following example lets you dump or load the contents of a database table. The procedure uses the DISABLE TRIGGERS statement to disable the appropriate triggers before each dump or load operation.
r-dstrig.p
|
Notes
- 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 OpenEdge Data Dictionary automatically disables the appropriate triggers during data dump and load operations.
- The Disable Delete Trigger (-
disabledeltrig) startup parameter disables the DELETE trigger when ALLOW-REPLICATION is on for the DISABLE TRIGGERS statement or the DISABLE-LOAD-TRIGGER() buffer method. For more information about this parameter, see Startup Command and Parameter Reference.