Bug #20367 | GRANT statements with host parameter broken? | ||
---|---|---|---|
Submitted: | 9 Jun 2006 19:56 | Modified: | 29 Nov 2006 14:31 |
Reporter: | eric | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Query Browser | Severity: | S3 (Non-critical) |
Version: | 1.1.20 | OS: | Windows (WinXP) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
Tags: | Source Editors |
[9 Jun 2006 19:56]
eric
[11 Jun 2006 7:35]
Valeriy Kravchuk
Thank you for a problem report. Sorry, but you really have error in your second statement: GRANT SELECT ON 'test'.* TO user@'%'; And you'll see the same error message in mysql client. You have to write that as (note backticks!): GRANT SELECT ON `test`.* TO user@'%'; or GRANT SELECT ON test.* TO user@'%'; If you correct your second statement, your script will work in QB 1.1.20.
[11 Jun 2006 13:51]
eric
I have tried your suggestion (both removing the single ticks and replacing them with backticks) with no change in behavior. Furthermore, as I stated in the original bug report, the script does indeed work unmodified (and modified) in the commandline client. I will attach screenshots shortly, but as far as I can tell I'm using legal syntax. Are you running Linux or other OS? Perhaps that could account for why your changes worked for you when you tested them, but they do not work for me. I've also tried changing the username in case the term 'user' is causing problems, but that didn't help either.
[11 Jun 2006 13:52]
eric
Screenshot of 1.1.20 failing to work with modified script
Attachment: mysqlqb-bug20367.png (image/png, text), 61.75 KiB.
[11 Jun 2006 13:53]
eric
MySQL command line client executing same script w/ no problems
Attachment: mysqlqb-bug20367-cmdlinetest.png (image/png, text), 13.48 KiB.
[13 Jun 2006 11:07]
Valeriy Kravchuk
Sorry, you are right. The following statements: GRANT USAGE ON *.* TO user@'%' IDENTIFIED BY 'whatever'; GRANT SELECT ON `test`.* TO user@'%'; also does NOT work in Script tab of QB 1.1.20. I've got the same error message as on your screenshot. It is a bug. I checked them last time as two different statements, one by one (hence different result I've got)...
[29 Nov 2006 14:31]
Mike Lischke
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at http://www.mysql.com/downloads/