Rechercher dans le manuel MySQL
24.3.1 Trigger Syntax and Examples
To create a trigger or drop a trigger, use the
CREATE TRIGGER
or
DROP TRIGGER
statement, described
in Section 13.1.22, “CREATE TRIGGER Syntax”, and
Section 13.1.34, “DROP TRIGGER Syntax”.
Here is a simple example that associates a trigger with a table,
to activate for INSERT
operations.
The trigger acts as an accumulator, summing the values inserted
into one of the columns of the table.
- Query OK, 0 rows affected (0.03 sec)
- Query OK, 0 rows affected (0.01 sec)
The CREATE TRIGGER
statement
creates a trigger named ins_sum
that is
associated with the account
table. It also
includes clauses that specify the trigger action time, the
triggering event, and what to do when the trigger activates:
The keyword
BEFORE
indicates the trigger action time. In this case, the trigger activates before each row inserted into the table. The other permitted keyword here isAFTER
.The keyword
INSERT
indicates the trigger event; that is, the type of operation that activates the trigger. In the example,INSERT
operations cause trigger activation. You can also create triggers forDELETE
andUPDATE
operations.The statement following
FOR EACH ROW
defines the trigger body; that is, the statement to execute each time the trigger activates, which occurs once for each row affected by the triggering event. In the example, the trigger body is a simpleSET
that accumulates into a user variable the values inserted into theamount
column. The statement refers to the column asNEW.amount
which means “the value of theamount
column to be inserted into the new row.”
To use the trigger, set the accumulator variable to zero, execute
an INSERT
statement, and then see
what value the variable has afterward:
- +-----------------------+
- | Total amount inserted |
- +-----------------------+
- | 1852.48 |
- +-----------------------+
In this case, the value of @sum
after the
INSERT
statement has executed is
14.98 + 1937.50 - 100
, or
1852.48
.
To destroy the trigger, use a DROP
TRIGGER
statement. You must specify the schema name if
the trigger is not in the default schema:
If you drop a table, any triggers for the table are also dropped.
Trigger names exist in the schema namespace, meaning that all triggers must have unique names within a schema. Triggers in different schemas can have the same name.
It is possible to define multiple triggers for a given table that
have the same trigger event and action time. For example, you can
have two BEFORE UPDATE
triggers for a table. By
default, triggers that have the same trigger event and action time
activate in the order they were created. To affect trigger order,
specify a clause after FOR EACH ROW
that
indicates FOLLOWS
or
PRECEDES
and the name of an existing trigger
that also has the same trigger event and action time. With
FOLLOWS
, the new trigger activates after the
existing trigger. With PRECEDES
, the new
trigger activates before the existing trigger.
For example, the following trigger definition defines another
BEFORE INSERT
trigger for the
account
table:
- FOR EACH ROW PRECEDES ins_sum
- Query OK, 0 rows affected (0.01 sec)
This trigger, ins_transaction
, is similar to
ins_sum
but accumulates deposits and
withdrawals separately. It has a PRECEDES
clause that causes it to activate before
ins_sum
; without that clause, it would activate
after ins_sum
because it is created after
ins_sum
.
Within the trigger body, the OLD
and
NEW
keywords enable you to access columns in
the rows affected by a trigger. OLD
and
NEW
are MySQL extensions to triggers; they are
not case-sensitive.
In an INSERT
trigger, only
NEW.
can be
used; there is no old row. In a col_name
DELETE
trigger,
only OLD.
can be used; there is no new row. In an col_name
UPDATE
trigger, you can use
OLD.
to
refer to the columns of a row before it is updated and
col_name
NEW.
to
refer to the columns of the row after it is updated.
col_name
A column named with OLD
is read only. You can
refer to it (if you have the SELECT
privilege), but not modify it. You can refer to a column named
with NEW
if you have the
SELECT
privilege for it. In a
BEFORE
trigger, you can also change its value
with SET NEW.
if you have the
col_name
=
value
UPDATE
privilege for it. This means
you can use a trigger to modify the values to be inserted into a
new row or used to update a row. (Such a SET
statement has no effect in an AFTER
trigger
because the row change will have already occurred.)
In a BEFORE
trigger, the NEW
value for an AUTO_INCREMENT
column is 0, not
the sequence number that is generated automatically when the new
row actually is inserted.
By using the BEGIN ...
END
construct, you can define a trigger that executes
multiple statements. Within the BEGIN
block,
you also can use other syntax that is permitted within stored
routines such as conditionals and loops. However, just as for
stored routines, if you use the mysql program
to define a trigger that executes multiple statements, it is
necessary to redefine the mysql statement
delimiter so that you can use the ;
statement
delimiter within the trigger definition. The following example
illustrates these points. It defines an UPDATE
trigger that checks the new value to be used for updating each
row, and modifies the value to be within the range from 0 to 100.
This must be a BEFORE
trigger because the value
must be checked before it is used to update the row:
- mysql> delimiter //
- mysql> delimiter ;
It can be easier to define a stored procedure separately and then
invoke it from the trigger using a simple
CALL
statement. This is also
advantageous if you want to execute the same code from within
several triggers.
There are limitations on what can appear in statements that a trigger executes when activated:
The trigger cannot use the
CALL
statement to invoke stored procedures that return data to the client or that use dynamic SQL. (Stored procedures are permitted to return data to the trigger throughOUT
orINOUT
parameters.)The trigger cannot use statements that explicitly or implicitly begin or end a transaction, such as
START TRANSACTION
,COMMIT
, orROLLBACK
. (ROLLBACK to SAVEPOINT
is permitted because it does not end a transaction.).
See also Section C.1, “Restrictions on Stored Programs”.
MySQL handles errors during trigger execution as follows:
If a
BEFORE
trigger fails, the operation on the corresponding row is not performed.A
BEFORE
trigger is activated by the attempt to insert or modify the row, regardless of whether the attempt subsequently succeeds.An
AFTER
trigger is executed only if anyBEFORE
triggers and the row operation execute successfully.An error during either a
BEFORE
orAFTER
trigger results in failure of the entire statement that caused trigger invocation.For transactional tables, failure of a statement should cause rollback of all changes performed by the statement. Failure of a trigger causes the statement to fail, so trigger failure also causes rollback. For nontransactional tables, such rollback cannot be done, so although the statement fails, any changes performed prior to the point of the error remain in effect.
Triggers can contain direct references to tables by name, such as
the trigger named testref
shown in this
example:
- );
- delimiter |
- END;
- |
- delimiter ;
- (0), (0), (0), (0), (0), (0), (0), (0), (0), (0);
Suppose that you insert the following values into table
test1
as shown here:
- (1), (3), (1), (7), (1), (8), (4), (4);
- Query OK, 8 rows affected (0.01 sec)
As a result, the four tables contain the following data:
- +------+
- | a1 |
- +------+
- | 1 |
- | 3 |
- | 1 |
- | 7 |
- | 1 |
- | 8 |
- | 4 |
- | 4 |
- +------+
- +------+
- | a2 |
- +------+
- | 1 |
- | 3 |
- | 1 |
- | 7 |
- | 1 |
- | 8 |
- | 4 |
- | 4 |
- +------+
- +----+
- | a3 |
- +----+
- | 2 |
- | 5 |
- | 6 |
- | 9 |
- | 10 |
- +----+
- +----+------+
- | a4 | b4 |
- +----+------+
- | 1 | 3 |
- | 2 | 0 |
- | 3 | 1 |
- | 4 | 2 |
- | 5 | 0 |
- | 6 | 0 |
- | 7 | 1 |
- | 8 | 1 |
- | 9 | 0 |
- | 10 | 0 |
- +----+------+
Traduction non disponible
Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-trigger-syntax.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.