Forum Replies Created
-
AuthorPosts
-
emaMember
Thank you, everybody!
emaMember'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.
emaMember'peterlaursen' wrote on '11:ALTER PROCEDURE statement cannot be used, refer to:
It is not the answer to my question. Maybe, I couldn't explain very well. π
Anyway thanks!
emaMember'vishal.pr' wrote on '11:Hi,
We understood your requirement. […] privilege.
Thanks to you, even though the bad news π
I think I could add a suggestion in the appropriate forum branch…
Making the feature optional, I think it would not be so unsafe as you wrote.
emaMember'peterlaursen' wrote on '10:Please tell: did you rename the SP when editing? Β Or are you telling that (temporarily) DROPPING it will remove the privilege to it?
I didn't rename the SP.
I say that: we know there's no a real ALTER command for SP.
The standar way i know to alter object like SP is, in practice, doing 2 steps: drop the SP (the drop of one object implies the delete of its grants) and create the modified version.
I used in the past other editing tools (for different dataserver than MySQL): while editing an object like SP, they automatically remember grants existing before the drop and re-apply them after the create.
That is, the sequence of sql statements they execute to alter a SP includes “grant execute” command too, at the end (if grants did exist previously).
I don't know if it's possible with SQLyog too. If so, i didn't find the way.
Thanks for your interest!
-
AuthorPosts