Bug #62112 Mysql workbench not showing tables
Submitted: 8 Aug 2011 10:32 Modified: 7 Mar 2012 14:38
Reporter: Bob Lawn Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.2.34 OS:Any
Assigned to: CPU Architecture:Any
Tags: tables

[8 Aug 2011 10:32] Bob Lawn
Description:
This bug was originally flagged up as bug ID 49916, but the status looks like it has been closed, however it still exists.

The issue is that upon making a connection to my database I don't see the tables, views or routines listed in the Schemata window.

Previous answers to this issue indicated that it was due to the mysql version running on the server, but I am running 5.0.92 and still experiencing the same problem.

How to repeat:
Just installed the latest version.
[8 Aug 2011 10:53] MySQL Verification Team
Thank you for the bug report. Are you able to login using same user/host/password with the mysql.exe client and your able to see the tables?. Thanks.
[9 Aug 2011 0:25] MySQL Verification Team
Use the same data which you used with Workbench when setting the connection:

mysql -uusername -hhost --port=3306 -ppassword

user your own values for: username, host, 3306, password

Thanks.
[24 Aug 2011 20:09] Rafael Antonio Bedoy Torres
Hi Bob,

Can you please let us know how big is your data base?, the problem is with all the databases or just one?

Thanks in advance.
[24 Sep 2011 23:01] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[6 Feb 2012 16:54] Mauricio Avendano
I download latest version of Workbench, and I cannot see the tables using the Query Borwser. I download mysql-gui-tools-noinstall-5.0-r17-win32.zip with same results. What version of tools can I used that works?

Thanks
[7 Feb 2012 14:38] Valeriy Kravchuk
Mauricio,

you should use Workbench 5.2.37.
[8 Mar 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".