> From: Jim Starkey
> The mechanism consists of another clause on trigger definitions
> ( class <trigger_class_name> ) and two two DDL systems
> "enable <trigger_class_name>" and "disable <trigger_class_name>".
> Yes, a trigger may be a member of an arbitrary number of classes.
>
> The disable statement disables triggers of the given name for
> either the duration of connection or until the trigger class
> is explicitly enabled with the enable trigger class statement.
>
> Trigger classes are not explicitly declared, just used.

Is trigger_class enabling/disabling restricted to table owner,
or is there some way how to restrict this functionality
to selected users (something like "grant class_name to user ...") ?

Ivan