I blinking hate MySQL

[d000hg]

mySQL workbench is a pile of cack if you ask me, query browser and adminstrator are great tools and as good as any DB tools I use on 'serious' databases.

I got workbench assuming as the 'official' tool it would be decent - it's OK but not a patch on the tools I'm used to like SQLDeveloper. I used to use TOAD with Oracle, I see there is a MySQL version - anyone tried it?

And I know MySQL is a powerful, capable RDBMS for real-world use - it's just making me grumpy!

[blacjac]

I've used Navicat for MySQL a couple of times and found it quite good.

Never used it in anger though....

[NickFitz]

I've used Navicat for MySQL a couple of times and found it quite good.

Never used it in anger though....

I've used Navicat on good-sized databases (hundreds of thousands of records) and it worked well. However I find the current incarnation of Workbench is OK - it's basically Query Browser and Administrator munged together in one app, and the front page for managing connections is a bit cruddy, but the DB management stuff is fine and the Query Browser-equivalent bits are superior to Query Browser IMHO.

All this is about the Mac versions, so other platforms may vary.

[administrator]

I use SQLYog:
MySQL GUI Tools. MySQL Monitor and Manager

Can't live without it now, more than worth the cost IMO.

[d000hg]

I've used Navicat on good-sized databases (hundreds of thousands of records) and it worked well. However I find the current incarnation of Workbench is OK - it's basically Query Browser and Administrator munged together in one app, and the front page for managing connections is a bit cruddy, but the DB management stuff is fine and the Query Browser-equivalent bits are superior to Query Browser IMHO.

All this is about the Mac versions, so other platforms may vary.

It seems a decent basic SQL tool with a few bits glued on like editing a table in a form. I miss stuff like autocomplete though... is it 'game_id' or 'id', etc.

I don't like the export though, it seems to insist on exporting everything with fully qualified names (db_name.table_name) and procedures with DEFINERs for the creating user. Makes for a few headaches (maybe there are options I didn't see).