MySQL Bugs: #27572: Unclear error message during non-root login with "SHOW DATABASES" disabled

Bug #27572	Unclear error message during non-root login with "SHOW DATABASES" disabled
Submitted:	1 Apr 2007 17:04	Modified:	17 Feb 2009 15:25
Reporter:	Bill O'Brien	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.2.10/1.2.11	OS:	Windows (Windows XP SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When "SHOW DATABASES" is disabled and a non-root user attempts to log into MySQL Query Browser on Windows XP SP2, an error is returned:

"Access violation at address 00352F02 in module 'libmysqlx.dll'. Read address 00000004"

After pressing "OK", program functions as normal, except for blank Schemata sidebar.  (The blank Schemata sidebar is the intended function of the disabled "SHOW DATABASES" configuration, I assume.)

How to repeat:
Disable "SHOW DATABASES" command.
Log into MySQL Query Browser with any non-root login.

Suggested fix:
In this context, change from an error to a warning along the the lines of "Schemata listing disabled in MySQL configuration."

This is with MySQL Server 5.0.37-community-nt

I should clarify that "functions as normal" was a very brief test -- I could switch databases by executing a USE command and was able to run other basic queries.  As far the error/warning distinction goes I'm not a developer, just an end-user, so I'm assuming this is cosmetic and not something deeper.

Changed severity, because "Access violation" is a bug in any case.

Thank you for the bug report.

Just a reminder that this is still happening in the latest GUI tools (Query Browser 1.2.12).  It is annoying because it keeps the tool from being fully functional in a hosted environment where account doesn't have the 'show databases' privilege.  The account only has access to the one database that the connection was made to and should be able to display schema info for that one database without having to show all databases.

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/