TRIGGER_NAME: The name of the database in which the trigger occurs and the trigger name, respectively.
EVENT_MANIPULATION: The trigger event. This is the type of operation on the associated table for which the trigger activates. The value is
'INSERT'(a row was inserted),
'DELETE'(a row was deleted), or
'UPDATE'(a row was modified).
EVENT_OBJECT_TABLE: As noted in Section 20.3, “Using Triggers”, every trigger is associated with exactly one table. These columns indicate the database in which this table occurs, and the table name, respectively.
ACTION_ORDER: The ordinal position of the trigger's action within the list of triggers on the same table with the same
ACTION_TIMINGvalues. Before MySQL 5.7.2, this value is always
0because it is not possible for a table to have more than one trigger with the same
ACTION_STATEMENT: The trigger body; that is, the statement executed when the trigger activates. This text uses UTF-8 encoding.
ACTION_ORIENTATION: Always contains the value
ACTION_TIMING: Whether the trigger activates before or after the triggering event. The value is
ACTION_REFERENCE_NEW_ROW: The old and new column identifiers, respectively. This means that
ACTION_REFERENCE_OLD_ROWalways contains the value
ACTION_REFERENCE_NEW_ROWalways contains the value
CREATED: The date and time when the trigger was created. This is a
TIMESTAMP(2)value (with a fractional part in hundredths of seconds) for triggers created in MySQL 5.7.2 or later,
NULLfor triggers created prior to 5.7.2.
SQL_MODE: The SQL mode in effect when the trigger was created, and under which the trigger executes. For the permitted values, see Section 5.1.7, “Server SQL Modes”.
DEFINER: The account of the user who created the trigger, in
CHARACTER_SET_CLIENT: The session value of the
character_set_clientsystem variable when the trigger was created.
COLLATION_CONNECTION: The session value of the
collation_connectionsystem variable when the trigger was created.
DATABASE_COLLATION: The collation of the database with which the trigger is associated.
The following columns currently always contain
Example, using the
ins_sum trigger defined in
Section 20.3, “Using Triggers”:
SELECT * FROM INFORMATION_SCHEMA.TRIGGERS->
WHERE TRIGGER_SCHEMA='test' AND TRIGGER_NAME='ins_sum'\G*************************** 1. row *************************** TRIGGER_CATALOG: def TRIGGER_SCHEMA: test TRIGGER_NAME: ins_sum EVENT_MANIPULATION: INSERT EVENT_OBJECT_CATALOG: def EVENT_OBJECT_SCHEMA: test EVENT_OBJECT_TABLE: account ACTION_ORDER: 1 ACTION_CONDITION: NULL ACTION_STATEMENT: SET @sum = @sum + NEW.amount ACTION_ORIENTATION: ROW ACTION_TIMING: BEFORE ACTION_REFERENCE_OLD_TABLE: NULL ACTION_REFERENCE_NEW_TABLE: NULL ACTION_REFERENCE_OLD_ROW: OLD ACTION_REFERENCE_NEW_ROW: NEW CREATED: 2013-07-05 07:41:21.26 SQL_MODE: NO_ENGINE_SUBSTITUTION DEFINER: me@localhost CHARACTER_SET_CLIENT: utf8 COLLATION_CONNECTION: utf8_general_ci DATABASE_COLLATION: latin1_swedish_ci