List:General Discussion« Previous MessageNext Message »
From:Ian Sales (DBA) Date:January 6 2006 5:34pm
Subject:Re: triggers on 5.0.17 -- definer not fully qualified
View as plain text  
Gleb Paharenko wrote:

>Hello.
>
>
>
>  
>
>>I've subsequently upgraded the instance to 5.0.18,
>>    
>>
>
>
>
>Have you updated master to 5.0.18 as well?
>
>  
>
- 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


-- 
+-------------------------------------------------------------------+
| Ian Sales                                  Database Administrator |
|                                                                   |
|                              "All your database are belong to us" |
| ebuyer                                      http://www.ebuyer.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