Information Schema TRIGGERS Table
Contents
The Information Schema TRIGGERS table contains information about triggers.
It has the following columns:
| Column | Description |
|---|---|
TRIGGER_CATALOG | Always def. |
TRIGGER_SCHEMA | Database name in which the trigger occurs. |
TRIGGER_NAME | Name of the trigger. |
EVENT_MANIPULATION | The event that activates the trigger. One of INSERT, UPDATE or 'DELETE. |
EVENT_OBJECT_CATALOG | Always def. |
EVENT_OBJECT_SCHEMA | Database name on which the trigger acts. |
EVENT_OBJECT_TABLE | Table name on which the trigger acts. |
ACTION_ORDER | Indicates the order that the action will be performed in (of the list of a table's triggers with identical EVENT_MANIPULATION and ACTION_TIMING values). Before MariaDB 10.2.3 introduced the FOLLOWS and PRECEDES clauses, always 0 |
ACTION_CONDITION | NULL |
ACTION_STATEMENT | Trigger body, UTF-8 encoded. |
ACTION_ORIENTATION | Always ROW. |
ACTION_TIMING | Whether the trigger acts BEFORE or AFTER the event that triggers it. |
ACTION_REFERENCE_OLD_TABLE | Always NULL. |
ACTION_REFERENCE_NEW_TABLE | Always NULL. |
ACTION_REFERENCE_OLD_ROW | Always OLD. |
ACTION_REFERENCE_NEW_ROW | Always NEW. |
CREATED | Always NULL. |
SQL_MODE | The SQL_MODE when the trigger was created, and which it uses for execution. |
DEFINER | The account that created the trigger, in the form user_name@host_name |
CHARACTER_SET_CLIENT | The client character set when the trigger was created, from the session value of the character_set_client system variable. |
COLLATION_CONNECTION | The client collation when the trigger was created, from the session value of the collation_connection system variable. |
DATABASE_COLLATION | Collation of the associated database. |
Queries to the TRIGGERS table will return information only for databases and tables for which you have the TRIGGER privilege. Similar information is returned by the SHOW TRIGGERS statement.
See also
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
