MySQL Editor Hangs on attempt to Launch

MySQLmysql-workbench

I have just downloaded the latest Community Installer (5.5.27) along with the MySQL WorkBench (5.2.41). I clicked OK on all default settings on setup.

When I try to "Open a connection to start querying" on the WorkBench home page and chose "Local Instance MySql 55", I keep getting stuck on a never-ending "Opening SQL Editor" screen ("An SQL Editor instance for "Local Instance MySql 55" is opening and should be available in a moment")

Any idea on what could be wrong ?

EDIT :
I am able to access it from command line and query it successfully. But still not from query editor.

Best Answer

Thanks Mika, I tried your solution in workbench (5.2.41). It worked after I cleared the passwords in the vault (click Manage Connections) and restarted the WorkBench.

To clear passwords stored in the vault, I did the following:

Open MySQL WorkBench the you will see the home page
Click Manage Connection at bottom left corner.
In Manage DB Connections, click Clear button besides Store in Vault...
Close it and restart WorkBench.
Double click Local instance mysql in home page, now you db will popup.

Related Solutions

MySQL Subquery hangs / terrible perfomance

The query is slow because the dateindex is used and that is not the best index for this query (or no index at all, please fix the EXPLAIN output). When the subquery is executed, the inventory_ID is already known and the price_type_ID is fixed but there is no composite index that can make this information useful.

Possible explanations for the single query running faster is that you either get cached results from previous execution of the query or it uses different index (and by luck this is a bit more efficient than the dateindex). You have several indexes, on (price_type_ID), on (inventory_ID) but no composite one. So, depending on statistics, the actual parameters and the index chosen each time, the performance will vary.

Try adding an index that will always do an index seek, no index or table scan (and get the price from the index, too, so no additional read form the table will be needed) and thus make both the query and the single query much faster:

ALTER TABLE _inventory_prices 
  ADD INDEX price_type_ID__inventory_ID__date__brutto__IX        -- choose a name
    (price_type_ID, inventory_ID, price_date, price_brutto) ;

MySQL Identifying Connection Attempt

MySQL does not have a way to determine the information you're looking for (client attempting the connection). The only thing you will get from a direct connection attempt is the username and hostname (as noted above).

MySQL doesn't utilize or pass User-Agent-like data in that manner.

Best Answer

Related Solutions

MySQL Subquery hangs / terrible perfomance

MySQL Identifying Connection Attempt

Related Question