Bug #66521 | Don't fetches tables list on database | ||
---|---|---|---|
Submitted: | 24 Aug 2012 8:42 | Modified: | 29 Jan 2013 3:45 |
Reporter: | Serg Udv | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.42 | OS: | Windows (Microsoft Windows XP Professional Service Pack 3 (build 2600)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | WBBugReporter |
[24 Aug 2012 8:42]
Serg Udv
[24 Aug 2012 20:13]
Rafael Antonio Bedoy Torres
Hello Serg, Can you please share with us how many schemas and tables you have on your DB? Thanks in advance!
[27 Aug 2012 8:09]
Serg Udv
I found that this only appears when I connect to MySQL server on FreeBSD 8.2. It contains 7 databases. Maximum 130 tables in the database. When connecting to a MySQL server on Windows 2008 to the same database no such problem. User has full priveleges. I can't fetch list of tables in objects browser for any databases on this server. I can see a list of tables in the list of suggestions when I type a query in the SQL Editor.
[27 Aug 2012 10:57]
Serg Udv
I has connected to the same MySQL server on FreeBSD 8.2 from another computer. In MySQL Workbench 5.2.31(!!!) I has got a list of tables in the object browser, but only for schema by default. If schema has not selected by default, i see "fetching..."
[28 Aug 2012 9:18]
Valeriy Kravchuk
What exact MySQL server version, 5.x.y, do you have on FreeBSD 8.2?
[30 Aug 2012 12:25]
Serg Udv
MySQL 5.1.49
[8 Sep 2012 17:09]
Baldemar Campoy
Hello, i have the same problem on windows 7 home profesional
[16 Sep 2012 1:56]
MySQL Verification Team
Please try version 5.2.43 . Thanks.
[19 Sep 2012 19:15]
Serg Udv
In workbench version 5.2.43 exact same problem
[29 Dec 2012 3:45]
MySQL Verification Team
Please try version 5.2.45. Thanks.
[30 Jan 2013 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".