Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.2-3, 10.2.2-2, 10.2.2-4
Description
Many triggers for the same event per table (e.g. many BEFORE DELETE triggerts).
This can be ported from 5.7
Looked at the MySQL 5.7 implementation. Too complex and too many not needed changed and moving of things to different files that make it very hard to follow code changes over time.
Will do this with new code, but will take test cases from MySQL 5.7
New functionality:
- "Any" amount of same events
- New syntax with
{ FOLLOWS | PRECEDES } trigger_name
CREATE [OR REPLACE]
[DEFINER = { user | CURRENT_USER }]
TRIGGER [IF NOT EXISTS] trigger_name trigger_time trigger_event
ON tbl_name FOR EACH ROW
[{ FOLLOWS | PRECEDES }other_trigger_name ]
trigger_stmt
Attachments
Issue Links
- is part of
-
MDEV-10137 Providing compatibility to other databases
- Open
- relates to
-
MDEV-10915 Multiple triggers are not counted in Executed_triggers status variable
- Closed
-
MDEV-10916 In trigger's CREATED time microseconds are misinterpreted
- Closed
-
MDEV-10924 CREATE OR REPLACE TRIGGER which fails on PRECEDES/FOLLOWS drops the trigger, but isn't written to binlog; replication fails
- Closed
-
MDEV-10926 Extra dot (period) in the error text for ER_REFERENCED_TRG_DOES_NOT_EXIST
- Closed
-
MDEV-10930 FOLLOWS in lex.h is out of alphabetical order
- Closed
-
MDEV-10911 Make SHOW TRIGGERS to show triggers' action order
- Closed
-
MDEV-11033 "follows" does not show up in "show create trigger" output
- Closed