Re: triggers on 5.0.17 -- definer not fully qualified

[Gleb Paharenko]

Hello.

> I've subsequently upgraded the instance to 5.0.18,

Have you updated master to 5.0.18 as well?



Ian Sales (DBA) wrote:
> 
> After upgrading to 5.0.17, the triggers on one of my instances now break
> replication with a "definer is not fully qualified" error. I set the
> DEFINER in the CREATE TRIGGER statement to CURRENT_USER (i.e.,
> root@localhost), but the error still occurs. If I try setting the
> DEFINER to any other user, then I get "user does not have access"
> errors, irrespective of whether that user does or does not have the
> necessary privileges.
> 
> I've subsequently upgraded the instance to 5.0.18, but the error still
> occurs. I've also tried experimenting with setting the DEFINER as a
> specific user and then assigning INSERT, UPDATE, DELETE, SELECT and
> SUPER privileges to that user. To no avail.
> 
> Anyone have any ideas how to resolve this?
> 
> Thanks
> 
> - ian
> 
> 


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com