DEV Community

Cover image for Holy Crap, Let's Talk About Sequel Pro For a Sec

Holy Crap, Let's Talk About Sequel Pro For a Sec

Geoffrey Ward on September 16, 2019

The Problem With MySQL Recently, I was assigned a 2 week sprint as part of a dev team. We were to build an app from scratch (our first), from blan...
Read full post
Collapse
 
moopet profile image
Ben Sinclair •

Sequel Pro has a few problems:

  • it's Mac-only
  • it's GUI-only, so when you work on a foreign system you'll have to find something else, with a different interface, and learn that instead
  • it doesn't (didn't? I don't know if it's changed in the last year) support some later versions of MySQL and will crash horribly when you try to do something like open a new tab while connected
  • its roadmap explicitly said it wasn't going to fix those issues
  • the name is confusing to new users and project managers, since adding "pro" to the end of something is usually Mac-speak for "proprietary, and expensive", and implies that there's a non-pro version (which there isn't)
  • some long queries crash the world and you can't quit them

At my place, we switched to using Table Plus to get round the bugs in Sequel Pro, but that's not a wonderful solution either because it's non-free.

MySQL workbench is probably the best solution because it's cross-platform and free, but it has its own bugs (sometimes it even crashes the MySQL server, but that's more an indicator that the server needs work...)

Collapse
 
geoffreyianward profile image
Geoffrey Ward •

All fair points! To my credit- 1) I'm on a mac 2) It was refreshing to use a GUI after so much terminal spelunking 3) It does not support the newest versions of SQL PRO as far as I know, but we're using 5.7 so that wasn't an issue 4) I'm a greedy boy, and since SQL PRO fit my very specific needs, I love it.

I was looking at using MySQL workbench, actually...but the Sequel PRO docs were speaking to my immediate needs so I tried that out instead. I'll check out workbench next!