Description:
I have used GUI tools for Mac OS X since before the query browser was universal. I have used the bundle version r3 r4 r5 and now r6, and I have sent in bug reports to apple and MySQL. In every version listed, everytime I try to run a query that returns no recordset it just crashes. It can't handle no recordset being returned. It also can only handle a recordset being returned about 50-75% the time. It also only runs scripts 25-50% of the time. I am the senior DBA for a fairly large internet company, and my preferred platform is Mac OS X. Why can't someone even stablize QB enough to not crash when a null recordset is returned to the browser?
Also, when I run a stored procedure, it reports it as being an error, when in fact, it was successful. Very, very Disappointing.
Equally important to me is why can't QB return the query times as it does on the Windows version? I use a Mac OS X platform because the GUI is elegant enough, but all of my Unix command line tools (SSH etc...) are there, as our MySQL servers are 64-bit based. Since the distribution for Mac OS X is much more streamlined (all libs have to be distributed with it) this makes this kind of error being passed through at least 5 versions even more baffling.
I am using a 2.16Ghz MacBook Pro (Intel) with 2GB of RAM with Mac OS X 10.4.8.
What gives? I have to run Parallels Workstation with a copy of Windows to use your tools even 1/2 way effectively. My company wants to pay the platinum enterprise price for support, for a cluster, but I am not sure I can back them up, if your management tools are not going to work on my chosen platform.
How to repeat:
Simply open Query Browser on any Mac OS X 10.4.x (Intel) box (MacBook Pro 2.16Ghz) and submit a query that will never return a recordset. (Select * from users where user_id <> user_id) for example or return a large recordset, or run a script. Sometimes refreshing the schema will cause it to puke, and sometimes, simply copying and pasting a script into a script tab will cause it to crash.
Suggested fix:
It seems like the MySQL library API is old, or outdated. Our SQL servers are all 5.0.22 - 5.0.27, and it happens on all of them. MySQL administrator is solid as a rock.
