How to fix definer does not exist error 1449 MySQLKedarMarch 23, 2015 Explaining and providing solutions of MySQL error 1449: The user specified as a definer does not exist using SQL SECURITY INVOKER and DEFINER. View Post
Access Control in MySQL Stored Routines: DEFINER, INVOKER & SQL SECURITYKedarJanuary 30, 2012 MySQL Stored Routines (functions and procedures) are not only used for improving performance but also they’re handy when it comes to enhancing security and restricting user access. This post briefs… View Post
6 responses to “Access Control in MySQL Stored Routines: DEFINER, INVOKER & SQL SECURITY”
Thanks Keddar. A seemingly confusing concept made clear because of your article. Google brought me here and it seems it made the right recommendation
Really great article. I was not aware regarding this security breach earlier. Thanks a lot for sharing this.
Wow, I had problems trying to understand these two clauses, but now that I’ve read your article, everything looks very clear. Thanks a lot!
Glad it helped 🙂
Nice post.
You don’t need to do a FLUSH PRIVILEGES after a GRANT, and you also made a typo on that line.
Thanks pointing to the FLUSH PRIVILEGES, Daniel.
Pasting from DOC for ref.:
“If you modify the grant tables indirectly using account-management statements such as GRANT, REVOKE, or SET PASSWORD, the server notices these changes and loads the grant tables into memory again immediately.”