List:General Discussion« Previous MessageNext Message »
From:Gleb Paharenko Date:January 9 2006 1:13pm
Subject:Re: triggers on 5.0.17 -- definer not fully qualified
View as plain text  
Hello.

This should be interesting for you:
  http://bugs.mysql.com/bug.php?id=16266



Ian Sales (DBA) wrote:
> - unfortunately, the set up demands that the master stays at 4.0. I
> can't change that. The triggers were working in 5.0.16. It's the new
> DEFINER that was added with 5.0.17 that seems to be causing the problem.
> 
> - 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



Thread
triggers on 5.0.17 -- definer not fully qualifiedDBA)5 Jan
  • Re: triggers on 5.0.17 -- definer not fully qualifiedGleb Paharenko6 Jan
    • Re: triggers on 5.0.17 -- definer not fully qualifiedDBA)6 Jan
      • Re: triggers on 5.0.17 -- definer not fully qualifiedGleb Paharenko9 Jan
        • Re: triggers on 5.0.17 -- definer not fully qualifiedDBA)9 Jan