Spec-Zone .ru
спецификации, руководства, описания, API
|
|
Spec-Zone .ru
спецификации, руководства, описания, API
|
The TRIGGERS table
provides information about triggers. You can see results only for databases and tables for which you have the TRIGGER privilege.
INFORMATION_SCHEMA Name |
SHOW Name
|
Remarks |
|---|---|---|
TRIGGER_CATALOG |
def |
|
TRIGGER_SCHEMA |
||
TRIGGER_NAME |
Trigger |
|
EVENT_MANIPULATION |
Event |
|
EVENT_OBJECT_CATALOG |
def |
|
EVENT_OBJECT_SCHEMA |
||
EVENT_OBJECT_TABLE |
Table |
|
ACTION_ORDER |
0 |
|
ACTION_CONDITION |
NULL |
|
ACTION_STATEMENT |
Statement |
|
ACTION_ORIENTATION |
ROW |
|
ACTION_TIMING |
Timing |
|
ACTION_REFERENCE_OLD_TABLE |
NULL |
|
ACTION_REFERENCE_NEW_TABLE |
NULL |
|
ACTION_REFERENCE_OLD_ROW |
OLD |
|
ACTION_REFERENCE_NEW_ROW |
NEW |
|
CREATED |
NULL (0) |
|
SQL_MODE |
MySQL extension | |
DEFINER |
MySQL extension | |
CHARACTER_SET_CLIENT |
MySQL extension | |
COLLATION_CONNECTION |
MySQL extension | |
DATABASE_COLLATION |
MySQL extension |
Notes:
TRIGGER_SCHEMA and TRIGGER_NAME: The name of the database in which the trigger occurs and the
trigger name, respectively.
EVENT_MANIPULATION: The type of operation on the
associated table for which the trigger activates. One of the values 'INSERT' (a row was inserted), 'DELETE' (a
row was deleted), or 'UPDATE' (a row was modified).
EVENT_OBJECT_SCHEMA and EVENT_OBJECT_TABLE:
As noted in Section
19.3, "Using Triggers", every trigger is associated with exactly one table. These columns
contain the database in which this table occurs, and the table's name.
ACTION_ORDER: The ordinal position of the trigger's
action within the list of all similar triggers on the same table. Currently, this value is always 0, because it is not possible to have more than one trigger with the same
EVENT_MANIPULATION and ACTION_TIMING on the
same table.
ACTION_STATEMENT: The statement to be executed when the
trigger is invoked. This is the same as the text displayed in the Statement
column of the output from SHOW
TRIGGERS. Note that this text uses UTF-8 encoding.
ACTION_ORIENTATION: Always contains the value 'ROW'.
ACTION_TIMING: Whether the trigger activates before or
after the triggering statement. One of the two values 'BEFORE' or 'AFTER'.
ACTION_REFERENCE_OLD_ROW and ACTION_REFERENCE_NEW_ROW:
The old and new column identifiers, respectively. This means that ACTION_REFERENCE_OLD_ROW
always contains the value 'OLD' and ACTION_REFERENCE_NEW_ROW
always contains the value 'NEW'.
SQL_MODE: The SQL mode in effect when the trigger was
created or altered, 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 ' format. user_name'@'host_name'
CHARACTER_SET_CLIENT: The session value of the character_set_client
system variable when the trigger was created.
COLLATION_CONNECTION: The session value of the collation_connection
system 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 NULL:
ACTION_CONDITION, ACTION_REFERENCE_OLD_TABLE,
ACTION_REFERENCE_NEW_TABLE, and CREATED.
Example, using the ins_sum trigger defined in Section
19.3, "Using Triggers":
mysql>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: 0 ACTION_CONDITION: NULL ACTION_STATEMENT: SET @sum = @sum + NEW.amount ACTION_ORIENTATION: ROW ACTION_TIMING: BEFOREACTION_REFERENCE_OLD_TABLE: NULLACTION_REFERENCE_NEW_TABLE: NULL ACTION_REFERENCE_OLD_ROW: OLD ACTION_REFERENCE_NEW_ROW: NEW CREATED: NULL SQL_MODE: DEFINER: me@localhost CHARACTER_SET_CLIENT: utf8 COLLATION_CONNECTION: utf8_general_ci DATABASE_COLLATION: latin1_swedish_ci