Table Format

Use the table format to change the mode of all database objects of a specified type that have been defined on the same table or view.
(1)
Table Format

1+ ,
1 CONSTRAINTS
1 INDEXES
1 TRIGGERS
2  FOR?   'owner'  . table_object
1  %Modes for Constraints and Unique Indexes1
1  %Modes
for Triggers and Duplicate Indexes2
Element Description Restrictions Syntax
owner Owner of table Must own table Owner name
table_object Table or view on which objects are defined Must be a local table or view. Objects defined on a temporary table cannot be set to disabled or filtering modes. Identifier
This example disables all constraints defined on the cust_subset table:
SET CONSTRAINTS FOR cust_subset DISABLED;
In table format, you can change the modes of more than one database object type with a single statement. For example, this enables all constraints, indexes, and triggers that are defined on the cust_subset table:
SET CONSTRAINTS, INDEXES, TRIGGERS FOR cust_subset ENABLED;
In HCL OneDB™ 10.00 and in earlier versions, you cannot use the SET TRIGGERS option of the SET Database Object Mode statement to disable an inherited trigger selectively within a table hierarchy. In this release, however, disabling a trigger on a table within a hierarchy has no effect on inherited triggers. For example, the following statement disables all triggers on the specified subtable, but the statement has no effect on triggers on table objects that are above or below subtable within a table hierarchy:
SET TRIGGERS FOR subtable DISABLED;

In cluster environments, however, the SET TRIGGERS, SET INDEXES, and SET CONSTRAINTS statements are not supported on updatable secondary servers. Session-level index, trigger, and constraint modes that the SET Database Object Mode statement specifies are not redirected for UPDATE operations on table objects in databases of secondary server