'peterlaursen' wrote on '12:
You are clear. The problem occurs if user editing the Stored Procedure does not have the GRANT privilege.
If user does not have GRANT privilege, he will receive an error during GRANT phase, but SQLyog will simply work just like now (drop+create will still work).
And if the user with no GRANT priv does not want errors, he can disable the feature in preferences…
But in a working scenario where the root is the only developer for many users (root has GRANT privilege), the feature would be appreciated (obviously, this is my case 🙂 )
Anyway, thanks! Every comment is welcome.