Bug #26271 Query Browser crashes with default db selected
Submitted: 11 Feb 2007 20:10 Modified: 28 Apr 2007 11:52
Reporter: Axel Muench Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Query Browser Severity:S1 (Critical)
Version:1.2.9 RC OS:MacOS (OSX 10.4.8)
Assigned to: Assigned Account CPU Architecture:Any

[11 Feb 2007 20:10] Axel Muench
Description:
MySql QB - select default db bug is back:

A - enter a default db in login screen 
or 
B - once logged in CTRL click in db pane to mark a db as the default db

1 - Then anytime something is enterd in the query pane the app crashes
2 - Double click a table for a query crashes the app instantly
3 - Drag an Drop a table in the query field for a quick query crashes the app instantly

How to repeat:
See above.
[12 Feb 2007 9:02] Sveta Smirnova
Thank you for the report.

On my Intel Mac all work fine. Please, indicate your CPU and if you connect to remote server.
[12 Feb 2007 19:50] Axel Muench
We connect to remote servers within our network and to servers outside of our network, we don't run a mysql db locally on our machines from which we run Query Browser on.
[13 Feb 2007 7:43] Sveta Smirnova
I still can not repeat the issue connecting to Windows server.

To which servers you connect to? Your Mac is PowerPC or IntelMac? Indicate version of MySQL servers you connect to also.
[13 Feb 2007 16:57] Axel Muench
MySQL Query Browser runs on Intel Dual Core MacBok Pros, MySQl database runs on Sun Microsystems machines with Solaris (mysql 4.1.21-standard-log) and others run on Mac PowerPC (mysql 4.1.7-standard)

New info: It seems to only crash on databases of the 4.x branch and not the 5.x ones
[28 Mar 2007 11:52] Sveta Smirnova
Please try with current r10 GUI Tools and if you can repeat provide configuration file for your mysqld.
[28 Apr 2007 23: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".