Bug #60981 MySql Workbench loading schema results in "fetching" shown for database
Submitted: 26 Apr 2011 15:38 Modified: 23 Jun 2013 2:07
Reporter: Tim Gilbert Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.33, 5.2.37, 5.2.38 OS:Linux (Ubuntu 10.10 x64)
Assigned to: CPU Architecture:Any
Tags: Fetching, schema, workbench

[26 Apr 2011 15:38] Tim Gilbert
Description:
When opening a Sql Editor window from MySQL Workbench, the workbench is unable to show the tables,views,stored procs that belong to that schema.  Instead the word "fetching..." is shown three times for each schema.  After waiting > 10 minutes, still no schema.

I am using the server on localhost as root with password.

I can still query and get responses (ie connection is made), I just can't use the visual tree on the left.

Running the workspace from terminal, I see these errors in stdout:

(mysql-workbench-bin:9177): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

(mysql-workbench-bin:9177): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

When using the classic Query Browser, this error does not exist and the list of tables load immediately and predictably.

Creating a new schema (fresh) with no child objects (tables/views/stored procs) exhibit the same behaviour.

How to repeat:
1) Launch Workbench
2) Create new connection to Start Querying (or use existing one)
3) Open a connection by double clicking on your connection.
4) Open one of the schema's on the left hand side by clicking on the black sideways arrow.

Observe that "fetching..." is shown three times rather than tables, views, procedures.

Suggested fix:
None.
[26 Apr 2011 15:39] Tim Gilbert
fetching... visual

Attachment: fetching.png (image/png, text), 12.34 KiB.

[26 Apr 2011 15:44] Tim Gilbert
It looks like I have Gtk 2.22.0 installed from the repo of ubuntu.
[26 Apr 2011 16:01] Alfredo Kojima
Did you upgrade MySQL recently? Did you run the mysql_upgrade script?
[26 Apr 2011 16:04] Tim Gilbert
Its possible that an update came via apt-get upgrade, I am not sure how I could check that...  Its my workstation, so I don't usually worry too much about just accepting any updates that come in.

I did try to run mysql_upgrade:

$ mysql_upgrade -u root -p
Enter password: 
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
This installation of MySQL is already upgraded to 5.1.49, use --force if you still need to run mysql_upgrade

I did not try to force.
[26 Apr 2011 16:12] Valeriy Kravchuk
So, server version is 5.1.49. How many tables do you have in the schema in question?
[26 Apr 2011 16:16] Tim Gilbert
In alertsdb, I have 21, in marketingdb I have 14 and in test, I have nothing.  I created that schema just to see if the problem presented itself with a newly created database.

To repeat, I can run queries against the schema's without problem so I don't think its actually a problem with the database (corruption, etc).

Also, if I use the depreciated MySQL Query Browser (v1.2.12) everything works as expected.

Thanks for your assistance in tracking this down.
[26 Apr 2011 16:45] Valeriy Kravchuk
See http://bugs.mysql.com/bug.php?id=60644 also. I wonder is this a duplicate? But with 3 schemata only and few tables in each of them it does not seem so...
[26 Apr 2011 17:25] Tim Gilbert
Those GTK errors seem interesting to me.  I am purely guessing, but the problem might be related to displaying that info, not in getting it.  The GTK errors seem to indicate a problem updating the tree.

(mysql-workbench-bin:9177): Gtk-CRITICAL **:
gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
[26 Apr 2011 18:58] Alfredo Kojima
The error messages are always displayed, even when fetching succeeds.
[26 Apr 2011 19:23] Tim Gilbert
Ok.  Good to know.  

I have tested this more and it does appear to be "server" related:  

*  My workstation connecting to localhost experiences the problem.  My workstation connecting to a remote mysql instance, everything is ok.
*  My laptop (running windows) connecting to my workstation, and the problem reappears in windows with a different version of workbench, but not for the default database, just for the others.

Very strange.  I will upload a screenshot showing the behavour of Windows laptop connecting to Ubuntu workation (the second situation).

Tim
[26 Apr 2011 19:24] Tim Gilbert
windows computer connecting to remote ubuntu server has a similar problem.

Attachment: screen 2.png (image/png, text), 25.10 KiB.

[5 May 2011 0:06] MySQL Verification Team
http://bugs.mysql.com/bug.php?id=61048 marked as duplicate of this one.
[16 May 2011 17:38] MySQL Verification Team
With a database with more than 5000 tables I got the fetching display but for few seconds (3-5 sec).
[1 Jun 2011 18:06] Rafael Antonio Bedoy Torres
verified
[3 Oct 2011 23:57] Andy Lawrence
I am seeing the same issue, get the same output:

(mysql-workbench-bin:15168): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

Appears to show fetching forever, doesn't seem to ever complete.

Workbench version 5.2.35 v7915
[11 Nov 2011 11:10] Sigfried Arnold
Same Problem here - after an Update to 5.5.17 MySQL Workbench stopped working.
[9 Feb 2012 10:03] Gatis Tomsons
On Ubuntu 11.10 with workbench 5.2.36 running "sudo mysql_upgrade -u root -p --force" fixed this problem. Note the "--force" option.
[10 Feb 2012 9:44] Enrico Piasente
Same problem: don't show table name, only "fetching".

MySQL Database 5.5.20 on WinXP
MySQL Workbench 5.2.37 on Win7 32bit
[1 Mar 2012 13:44] Kevin ultimate
Think this is same issue as http://bugs.mysql.com/bug.php?id=64500
[9 Mar 2012 14:47] Valeriy Kravchuk
Bug #64500 was marked as a duplicate of this one.
[10 Mar 2012 21:51] Marcelo Bello
I am affected by this very same bug.
Using Workbench 5.2.36 CE (rev 8542) for Windows 7 64. The error happens when I connect to MySQL database hosted on the same computer ('localhost connection').
I can do server admin just fine, but SQL Development section is useless because of this bug.
This is affecting me for many months now, I remember I have updated the software at least twice since noticing this issue for the first time.

This bug is quite bad and is going for a while, I wish it could get some priority.
[15 Mar 2012 16:21] Paweł Chuchmała
I have this issue on Windows (Workbench) and MySql (linux) - 5.5.21-log.

I can connect nad use MySql on Windows - 5.5.16
[28 Mar 2012 10:40] Patrick O'Gorman
I am getting this problem as well on version .38 on ubuntu 11.10 unity with remote connections to a centos 5.5 server.
[28 Mar 2012 19:53] Jeff Cook
I experienced this bug until I ran mysql-upgrade. Things are fine now after running that. I did not have to specify --force.

Using Arch Linux 3.2.13; mysql 5.5.21; mysql-workbench 1:5.2.38; gtk2 2.24.10.
[1 Jun 2012 7:43] Thorsten Scherer
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)
[23 Jun 2013 2:07] Alfredo Kojima
Duplicate of bug #65254

Note: This is caused by a badly installed MySQL server. More specifically, by the DB admin not running mysql_upgrade_dbs after uprading MySQL.