I’d love to see support dropped for Sequel Pro in Local for Mac and replaced with Sequel Ace. Better still, being able to set a default option for a SQL client in Local settings would be great. Support for a handful of apps across platforms would have to be built in though.
Needing to replace the socket with the dummy socket mentioned here in the my.cnf.hbs file. This works, but I’m wondering if there’s a more programatic way of going about this, or replacing it on the fly.
I’m wondering how to specify that we want to open Sequel Ace, and not another program. This was defaulting to Table+, then to Sequel Pro.
Since Sequel Ace was forked from Sequel Pro, I’m assuming the code is pretty similar. Is it possible to get a gist somewhere of the Sequel Pro connect code?
Also, is there a recommendation for switching out socket file references on the fly?
Once this add-on is done and working, I’m assuming it would be a good model on how to abstract the Sequel Pro code into an add-on, which I’d be happy to help with as well.
I did a little googling and it looks like @brandondove commented on an open issue with Sequel Ace:
If I understand the thread correctly, there’s a few things going on:
Sequel Ace isn’t able to connect to a database via sockets because it is running in sandbox mode
Sequel Ace is running in sandbox mode so that it can be listed in the App Store
TablePlus is able to connect over sockets because it isn’t running in sandbox mode – it’s something you manually download and install from the internet.
I’m not quite sure where to take this addon since connecting to sockets isn’t something that the Sequel Ace devs are able to take on at this point (at least until they aren’t distributing via the App Store).
@ben.turner I think the key here is the App Store connection. Hahaha, seems like a decent-sized feature to give up in order to be in the App Store. Oh well, I’ve subscribed to this thread and will also test some of the work arounds (perhaps one can be automated in the Local add-on).
Just following up here - thank you for raising this initially! Support for Sequel Pro has been removed within Local in v6.1.1. When updating to the latest version, you’ll see that disappear from the Database tab within a site. Adminer is the default option, and TablePlus can be installed from the Add-on library.
Installing via homebrew won’t change things. The developers of Sequel Ace are coding it in a way so that it can be available in the Apple App store. No matter where the application ends up (for example homebrew, or even some random website) the actual source code for Sequel Ace doesn’t allow for connecting to databases over sockets.
Hello! Is there any update regarding the ongoing issues with sequel ace support?
I know in the past the local team supported sequel pro.
Is there any support for sequel ace to connect to our local databases?
Does anyone know of a hacky way?
@Nick-B Hello Nick. Thank you for your response. I checked out those previous threads and could only find some hacky solutions and nothing definitive. This is why I wanted to start a new thread for some fresh ideas for an issue which must be frustrating many uses. Unless you see something on those threads that I am missing? Thank you again for your time.
I don’t have anything new to add myself, but for our devs to keep track of requests and information I’m going to merge your feature request with one of the previous ones to keep that information together.
I did check with our team however to confirm there are still no immediate plans for this, however insight and interest from the community can always sway things!
I originally opened the ticket and since there was no solution for a while, I switched to TablesPlus. The main reason is SequelAce can’t support Socket connections since it App store app. It’s paid, but there is also a TablesPlus LocalWP plugin to auto connect to the DB, which was was the main reason I used SequelPro originally.