Because triggers can be activated by a user attempt to insert, update, or delete data, no specific privileges are required to execute them.
When a user invokes a trigger, the user assumes the privileges of the owner of the table on which the trigger is defined. The action statements are executed on behalf of the table owner, not the user who activates the trigger. However, to create a trigger that uses a stored procedure requires at least one of the following conditions:
▪ creator has DBA privileges,
▪ creator is the owner of the table on which the trigger is being defined,
▪ creator is granted all privileges on the table.
If the creator has DBA authority and creates a trigger for another user, a solidDB server assumes that unqualified names specified in the TRIGGER statement belong to the user. For example, the following statement is executed under DBA authority:
CREATE TRIGGER A.TRIG ON EMP BEFORE UPDATE
Since the EMP table is unqualified, the solidDB server assumes that the qualified table name is A.EMP, not DBA.EMP.