Bug #5359 Schema cannot be accessed in MySQL Query Browser
Submitted: 2 Sep 2004 0:54 Modified: 1 Dec 2004 13:44
Reporter: David Mullin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Query Browser Severity:S2 (Serious)
Version:1.0.4 Alpha OS:Windows (Win XP)
Assigned to: Michael G. Zinner CPU Architecture:Any

[2 Sep 2004 0:54] David Mullin
Description:
I had been using the MySQL Query browser and quite liked it.  However, I can no longer access my databses using this tool.  They no longer appear in the "Schemata" window (right side of the window).  I have tried all three accounts that I have set up- same result.

MySQLAdmin (v1.4) shows that they are there.  I can click on the databse tab and access them with this tool.  In fact, I can access these database with TOAD for MySQL.  However, they no longer appear in Schemata...as though they are gone.

If I use one of my former queries (i.e. History Tab), to access one of the databses with a SELECT statement, I get the following message: 
"Access denied for user "@'%' to database 'world"

ALl three accounts that I was using to acces my databases produce the same response.  In fact, if I list one of theses "missing schemas" as the account login schemas, I get the same kind of message complaining about "user "A'%' to database ' world".

I have no idea what triggered this.  I simply went into to query browser and it only displays the "test" database- all the others are no longer displayed.  I am pointing to the right data directory and can access these databases using another client (e.g. TOAD) without a hitch.

How to repeat:
Sorry- I have no idea what brought this up.  I simply brought up the Query Browser like I have been doing- the databases were no longer displayed in the Schemata window.

I had set up a couple of test databases and accounts; used them a few times; now, my databases don't appear int eh Schemata window.
[3 Sep 2004 21:08] MySQL Verification Team
Hi,

Looks like you are connected as anonymous user, you can check it with:
SELECT CURRENT_USER();

If so, check your connection settings.