MySQL Bugs: #62086: Crashes with Unhandled exception setting a database to default schema

Bug #62086	Crashes with Unhandled exception setting a database to default schema
Submitted:	4 Aug 2011 18:02	Modified:	17 Nov 2011 19:04
Reporter:	david soo	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.34	OS:	MacOS (10.6.8 )
Assigned to:		CPU Architecture:	Any

Description:
attempt setting a database to be the default schema 

table schemas in side bar left as "fetching" 

attempt to refresh all 

get message:

Unhandled Exception

An unhandled exception has occurred: Type mismatch: expected object of type db.Schema, be got db.mysql.Schema

How to repeat:
attempt setting a database to be the default schema 

table schemas in side bar left as "fetching" 

attempt to refresh all

What exact server version, x.y.z, local or remote, are you working with? How many databases/schemata and tables are there, in total?

mysql version on server:

Ver 14.14 Distrib 5.1.54, for redhat-linux-gnu (x86_64) using readline 5.1

There are 32 databases on the server 
-- average of 70 tables per database
-- largest 79 tables
-- lowest 8 tables

remote on a hosted provider.

down-grading severity

Does it happen every time? With any database?

The day I logged this ticket, it would happen all the time on whatever database.

Close - restart - choose database - try refresh - crash...

Today:

start workbench - choose database to be default schema - right click on "Fetching..." and refresh - get Unhandled Exception message -- then crashes with message MySQL Workbench quit unexpectedly.

dump file attached

verified. when the refresh is initiated, while the schema-sub-items still read "Fetching..." an expetion appears for each attempt and each sub-item

Same here (Mac OS X 10.6.8, MacBook Pro 8,3 17" i7 2.2GHz 4GB RAM), but my installation only displays

"Fetching..."

for *every* schema, without crashing.

Mysql 5.5.16 CE x-64
Mysql WB 5.2.34 R 7780

If one knows the name of a table (and her fields) in a schema, a direct query correctly shows results.

Seems like the whole WB is a graphical version of Terminal.app.

It's a 64 bit only bootstrap OS X issue?!

Fixed as of 5.2.36:
+        After setting a default schema, choosing <guibutton>Refresh
+        all</guibutton> while the schema information is "fetching" would
+        result in an unhandled exception.