Updating of old row is not allowed in trigger
Triggers in different schemas can have the same name.
In addition to the requirement that trigger names be unique for a schema, there are other limitations on the types of triggers you can create.
The workaround for this is to use variables defined in packages to store information that must be in scope for all timing points.
In particular, you cannot have two triggers for a table that have the same activation time and activation event. This is also advantageous if you want to invoke the same routine from within several triggers.
The CREATE TRIGGER statement has a lot of permutations, but the vast majority of the questions I'm asked relate to basic DML triggers.
The trigger becomes associated with the table named was added in My SQL 5.0.2.
My SQL Enterprise For expert advice on creating triggers subscribe to the My SQL Enterprise Monitor. In My SQL 5.0 triggers, depending on whether there was a duplicate key for the row.