TRIGGER Privilege

GRANT

The following examples demonstrate grant of a single privilege. A single GRANT statement can grant multiple privileges at the same scope by providing a comma-separated list of the privileges.

To grant the TRIGGER privilege at global scope, replace the user specification ('USERNAME'@'HOSTNAME') in the following query to align to your requirements:

GRANT TRIGGER
  ON *.*
  TO 'USERNAME'@'HOSTNAME';

To grant the TRIGGER privilege at database scope, replace the user specification ('USERNAME'@'HOSTNAME') and database name (DATABASE_NAME) in the following query to align to your requirements:

GRANT TRIGGER
  ON DATABASE_NAME.*
  TO 'USERNAME'@'HOSTNAME';

To grant the TRIGGER privilege at table scope, replace the user specification ('USERNAME'@'HOSTNAME'), database name (DATABASE_NAME), and table name (TABLE_NAME) in the following query to align to your requirements:

GRANT TRIGGER
  ON DATABASE_NAME.TABLE_NAME
  TO 'USERNAME'@'HOSTNAME';

REVOKE

The following examples demonstrate revoke of a single previously-granted privilege. A single REVOKE statement can revoke multiple privileges at the same scope by providing a comma-separated list of the privileges.

To revoke the TRIGGER privilege at global scope, replace the user specification ('USERNAME'@'HOSTNAME') in the following query to align to your requirements:

REVOKE TRIGGER
  ON *.*
  FROM 'USERNAME'@'HOSTNAME';

To revoke the TRIGGER privilege at database scope, replace the user specification ('USERNAME'@'HOSTNAME') and database name (DATABASE_NAME) in the following query to align to your requirements:

REVOKE TRIGGER
  ON DATABASE_NAME.*
  FROM 'USERNAME'@'HOSTNAME';

To revoke the TRIGGER privilege at table scope, replace the user specification ('USERNAME'@'HOSTNAME'), database name (DATABASE_NAME), and table name (TABLE_NAME) in the following query to align to your requirements:

REVOKE TRIGGER
  ON DATABASE_NAME.TABLE_NAME
  FROM 'USERNAME'@'HOSTNAME';

SHOW Output

A user's privileges can be displayed using the SHOW GRANTS statement.

If the TRIGGER privilege is present, it will be shown as TRIGGER in the output. For example:

SHOW GRANTS FOR 'app_user'@'192.0.2.%';

+-------------------------------------------------------+
| Grants for app_user@192.0.2.%                         |
+-------------------------------------------------------+
| GRANT TRIGGER ON `app_db`.* TO 'app_user'@'192.0.2.%' |
+-------------------------------------------------------+

Privilege Failure

An error message is raised if an operation fails due to insufficient privileges. For example:

CREATE TRIGGER customer_pay
  BEFORE INSERT ON hq_sales.customer_payment
  FOR EACH ROW
  INSERT INTO hq_sales.customer (customer_id, customer_name,customer_email)
    VALUES (234, "person", "person@test.com");

ERROR 1045 (HY000): [11281] Permission denied: User 'USERNAME'@'HOSTNAME' is missing TRIGGER on `hq_sales`.`customer_payment`; transaction aborted