MySQL Bugs: #64500: Schemata structure not loading if localhost

Bug #64500	Schemata structure not loading if localhost
Submitted:	1 Mar 2012 2:28	Modified:	9 Mar 2012 14:46
Reporter:	Diogo Domanski	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.38	OS:	Linux (Ubuntu 11.10)
Assigned to:		CPU Architecture:	Any

Description:
Mysql Workbench SQL Editor fails on loading schema structure if connection is set up to localhost. The three schema child nodes in the schemas tree (Tables, Views and Routines) keeps on 'fetching...'.

The same does not occur when the connection is established with a remote server.

How to repeat:
1. Run mysql workbench
2. Click on 'Open Connection to Start Querying'
3. Fill in the connection parameters form (using 127.0.0.1 or localhost for Hostname field)
4. Click on 'Ok' button
5. Double click or expand any schema in the schemas list

Suggested fix:
As in a remote server connection, the schema items (Tables, Views and Routines) should be loaded for localhost connection

What exact server versions, x.y.z, do you use on localhost and on remote host where everything works as expected?

Valeriy,both servers (local and remote) are 5.1.58-1ubuntu1.

I have the same issue using workbench 5.2.38 connecting to 5.5.21 server (win 2003) both locally and remote (Win7 64bit client).
Issue does not occur when connecting to 5.1.34 server on the same server.

Duplicate of http://bugs.mysql.com/bug.php?id=60981 ?

Kevin, I guess so

Duplicate of bug #60981 probably.

Same behavior in MacOS 10.7.4

MySQL Workbench CE for Mac OS X version 5.2.40  revision 8790
Configuration Directory: ~/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.9.1
OS: Darwin 11.4.0
CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz, 4.0 GB RAM

Console Output:

MySQLWorkbench[1359:3a03] NSOutlineView Warning: reloadData called while in the middle of doing a reloadData (break on NSLog to debug)