The table I used in these examples has triggers with a non-SUPER user as DEFINER. So when the trigger tries to change data in an associated table, the trigger fails and the whole statement emits the above error message.
I've found this to be a general problem with triggers in MySQL: it's not clear from the error message if the original table or the trigger is causing problems.
But anyway, I think the above bug can be closed as bogus.
I've found the reason for the above behavior:
The table I used in these examples has triggers with a non-SUPER user as DEFINER. So when the trigger tries to change data in an associated table, the trigger fails and the whole statement emits the above error message.
I've found this to be a general problem with triggers in MySQL: it's not clear from the error message if the original table or the trigger is causing problems.
But anyway, I think the above bug can be closed as bogus.