List:General Discussion« Previous MessageNext Message »
From:Ian Sales (DBA) Date:January 5 2006 4:46pm
Subject:triggers on 5.0.17 -- definer not fully qualified
View as plain text  
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


-- 
+-------------------------------------------------------------------+
| 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