This mysql stored function will return you all the dates between given dates having specified day. In short if you say: give me all Sundays in this month. I have…
Are you tired of manually generating test data for your MySQL tables? If you’re looking for random data generator, look no further! Introducing the MySQL Random Data Generator, a powerful…
“I just learned that Agent K has been assassinated by Boris from future, an alien criminal in 1969. I must travel through a time and stop him and save young…
Ever come accoss a situation where you have to load a flat text file into MySQL with data provided in single column! Say, your data to be loaded in table…
Schema alteration is a big headache especially when it has already reached to production and things get worse when the relations are involved.Below is a short example for altering tables…
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…
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.”