Excellent work with the new foreign key support. I like the (->) arrow to jump to the data. Top notch feature.

Now all it needs is user management, and ways to see what query was just run (when adding foreign keys) and it’ll rival phpMyAdmin.

A few more suggestions:

* The same sorting functionality used for tables would be great for databases (change it from a dropdown to a select above the table list), and in the server variables screen would be neat too.

* A multi condition search functionality

* Rename/Copy database/table functionality

* Ability to set database type override (the default is MyISAM but I may want to always use InnoDB, but dont want to select it / remember to select it.

Hi Kieran,

Thanks for your suggestions. You’ll be glad to here that user management is currently being worked on by one of the developers and is nearing completion and so will most likely be included in the next version (0.9.7).

I’ve just completed implementing live searching of the server variables table so it might be included in the 0.9.6 release in a weeks time and multi-condition table filtering is definitely one of the next big things on our to do list so you can probably expect it within the next couple of versions.

Although renaming/copying is currently not available for databases, it is for tables, although copying a table is listed as ‘Duplicate’ in the menu. We’re also going to be looking into more advanced control over the options available when creating objects (i.e. databases, tables, etc).

Thanks again for your suggestions and if you have any more feel free to report them in the issue tracker linked in the post.

Cheers

Nice, SSH tunnel support will definitely come in handy for me. Now if only we could get PostgreSQL support.

Nice one!

All I need now is support for Public Key authentication for SSH and I can switch over completely to Sequel Pro!

Keep up the good work.

WOW!

This is coming along nicely!

The Relations command and Table info are very welcome additions. NIce work.

While a nice app, now I wish I had not paid for Meerkat, you’ve just added why I needed it.

J K: PostgreSQL is high on our priority list, but it’s a big job and will take time. More developers are always welcome — especially ones familiar with PostgreSQL.

Fredrik: public key authentication for SSH should be fully supported in this release – it should draw location settings etc from your default shell. If it’s a password-protected key, that should be supported as well – sharing keychain passwords with Terminal!

(I say “should” because I’m not sure I’ve caught every configuration possibility, but give it a shot)

Looking great so far.

One purely aesthetic item with the new table filter box:

When you have enough tables to make the list scroll, the top of the scrollbar itself sort of dangles in space.

Could be solved with a thin line separating the filterbox & the table list, same as the one that separates the table list from table info. Would give the top of the scrollbar something to “anchor” to.

Also when the window is inactive, the filter box background color remains the same blueish-gray color, while the rest of the side-bar changes to light gray.

Obviously not really a functional issue, just looks odd to me.

Thanks for everything so far and looking forward to more updates!

RowanB: Ah great, didn’t realize this.
However, when i try to connect to the host that i’ve configured in .ssh/config i get the following error:

debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type
debug1: permanently_drop_suid: 501
debug1: No more authentication methods to try.
read_passphrase: can’t open /dev/tty: Device not configured

any idea how to solve this issue?

Fredrik: interesting – in my limited experience, that suggests it found the key to try, but the key is password-protected (is that correct?). Sequel Pro should have prompted you for the password to the key if that’s the case, but what might be causing the problem is that you only have the connection timeout period (set in the prefs) to enter the password, as SSH appears to use a single timeout for everything. If that was the problem, I’ll have to find some way to work around that…

RowanB: the key is indeed password protected. And Sequel Pro prompts me for the password and then I get the error message. Can I tweak the config to fix this or do you have to change something in Sequel Pro?

Hi Fredrik,

We’ve made a couple of fixes following some further work – could you try RC2, now linked above, and see if it works for you with the public key?

Thanks!

RowanB: Just tried it, and it works like a charm!

Thanks alot, i’ve now switched 100% to Sequel Pro…

Love sequelpro! Loved cocoamysql back in the day, this is an excellent descendant project! Like it so much I’m willing to pay for a commercial version (1.0?)!

One suggestion pair on one topic, on top of the others posted above. This may well already be on the development map, and maybe someone else has already suggested it, but here’s my $0.02…

We need a better way of viewing and exporting NULLs. Ideally, a NULL value would display either nothing or the word NULL (instead of some string I get to set) BUT, to distinguish it from an empty but non-null value, should have a user-chosen background color for that field in that row. HeidiSQL (successor to the old MySQLfront) on Win has this and it makes it very easy to distinguish emptys from true nulls. I usually set it to some unsaturated, very light color (something like html color #dbe3e8), and it makes the NULLs clearly visible and distinguishable from empty values, while not interfering with the actual data nor being a color so loud that it distracts you from the rest of the data. But, if I wanted to use that color as a warning flag, the fact that said color would be a user preference item would allow me to set it to stop-sign red, or hunting jacket orange, or whatever other loud color if I so desired.

Also, regardless of what the null behavior is for viewing, the behavior for exporting should be something more sensible. It should be either empty or the word NULL (unquoted), perhaps as a user preference item of its own. As it stands, sequelpro exports whatever string I’ve set for null viewing. If I set, say, “—–” as that string, then my exported data will have many “—–” that I have to find/replace before the data is useable in my typical workflow.

That being said, this is by far the best mysql GUI project on Mac and clearly shows awesome future potential. Keep up the great work, guys!

Great big thanks guys!!