[REQ] Multiple RDBMS support #362

Open
sequelpro opened this Issue Nov 9, 2013 · 137 comments

Comments

Projects

Under Consideration in Sequel Pro 2.0

@ghost
Contributor

ghost commented Nov 9, 2013

Issue imported from Google Code: https://code.google.com/p/sequel-pro/issues/detail?id=362
Reporter:brandon....@gmail.com Date:2009-08-08 08:10:32 Status:Accepted

With the changes from 9.5 to 9.6, Sequel Pro is nearly flawless, and absolutely awesome. It is by far
my program of choice, but sometimes I have to deal with other RDBMSs, and I have to use some
second- or third-rate tool (which is usually not free). (I've used some tools that have more features
than Sequel Pro, but they're usually ugly and non-intuitive, probably designed for full-time DBAs,
not for developers.)

The name change from CocoaMySQL to Sequel Pro leaves open the possibility of supporting
databases other than MySQL. Of course you probably want to wait until after 1.0 to consider doing
this, but what about supporting SQLite and PostgreSQL? A lot of developers use SQLite locally, and
quite a few seem to be moving to Postgres.

I realize this feature belongs on the backlog, and not something to be done right away, but please
consider adding it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:stuart02 Date:2009-08-20 11:53:46

Adding support for multiple RDBMS is definitely on our to-do list, but as you can probably imagine is a major
undertaking involving a significant amount of development and so its probably safe to say that work on it won't
start until at least version 1.0 is released.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:vincent....@gmail.com Date:2010-02-08 15:14:37

would love to see postgres support

@ghost
Contributor

ghost commented Nov 9, 2013

Author:rowan.h...@gmail.com Date:2010-02-25 19:52:00

PostgreSQL Support would be absolutely fantastic

@ghost
Contributor

ghost commented Nov 9, 2013

Author:mjpta...@gmail.com Date:2010-03-10 14:28:46

add me as one more vote for postgres.

Even for some simply functionality.

With mysql now owned by oracle I am looking at moving to postgres.

However there is the new open source DB being developed by former mysql gurus - so it might be another
interesting option.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:levi...@gmail.com Date:2010-04-04 09:51:43

Same here! I'm moving to SQLite for local prototyping and I'm looking into moving to Postgres since Oracle
took over… I'm just stating this because I think Postgres (at least) support should be moved up in the to-do
list.

There are alternatives out there, but their prices are geared to the Enterprise, who's looking for same clients
for all platforms and don't bother looking for better, more affordable solutions. We, lone developers, are left
with little choice in terms of DB GUIs that are both powerful but also usable. You guys are doing an excellent
job with Sequel Pro and I can't wait for aforementioned support. :)

Okay, back to coding! :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:netsin...@gmail.com Date:2010-05-20 02:49:03

Postgres + Sequel Pro = happy.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:andrew.f...@gmail.com Date:2010-05-20 03:00:16

I'm in the same situation as levifig. I would love to see Postgres support for Sequel Pro. With Oracle taking over
Mysql, its future is obviously not very clear to say the least. Meanwhile Postgres has steadily been improving with
the beta's of 9.0 which will include better replication support.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:dhenne...@gmail.com Date:2010-06-24 08:00:05

+1 for this feature. MySQL is starting to smell like Oracle...

@ghost
Contributor

ghost commented Nov 9, 2013

Author:coldcac...@gmail.com Date:2010-07-02 11:47:27

Just to add my voice for PostgreSQL support. Would LOVE that! We're switching to PostgreSQL and I'm looking at Navicat at the moment - yuck! As has already been mentioned, I think in light of the MySQL and Oracle situation, PostgreSQL is a better fit for Sequel Pro!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:escarr...@gmail.com Date:2010-07-06 06:34:04

SQLite3 support would be super!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:vermyn...@gmail.com Date:2010-07-20 12:32:11

+1 for SQLite. I was actually considering the production of a brand new GUI client that looks just like this for SQLite, but I'm hoping you beat me to it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:mich...@lawler.id.au Date:2010-08-09 22:29:32

Would love to see support for Postgres

@ghost
Contributor

ghost commented Nov 9, 2013

Author:and.dam...@gmail.com Date:2010-08-10 02:29:05

in the meanwhile can anyone using sqlite suggest an alternative to Sequel Pro?

I'm using Firefox extension SQLite Mager in a XULRunner but it's not a Cocoa app and it feels a bit uncomfortable.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gene...@gmail.com Date:2010-08-16 14:07:14

Personally, I totally disagree with this request. It's better to stay focused on MySQL for a long while, and make a brilliant, feature-rich piece of software with flawless UI and no major bugs.

I'm afraid that if this request will be implemented, we could get yet another DBVisualizer.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:mcsno...@gmail.com Date:2010-10-14 07:38:59

postgresql support would be most valuable to me, followed by sqlite

@ghost
Contributor

ghost commented Nov 9, 2013

Author:lailso...@gmail.com Date:2010-11-04 07:47:25

Now that Oracle is deprecating MySQL (http://mysql.com/products/), it would be a great time to offer PostgreSQL support. I love Sequel Pro so much; it's the only reason for not switching to PostgreSQL right now.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:4braham Date:2010-11-04 22:28:49

MySQL is not deprecated. If you pay for MySQL you will have to pay more now but if you use the open source community version nothing has changed.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:brax...@braxtonbeyer.com Date:2010-11-05 08:02:36

except that you cant use InnoDB

@ghost
Contributor

ghost commented Nov 9, 2013

Author:rowanb@gmail.com Date:2010-11-05 08:17:05

"MySQL Classic" - an embedded database which requires a license to use commercially - doesn't come with InnoDB. This isn't to be confused with "MySQL Community Edition", the GPL version of MySQL, which continues to ship with InnoDB.

http://blogs.oracle.com/mysql/2010/11/mysql_community_edition_and_innodb.html

Back on-topic, we do continue to plan support for multiple RDBMSes, but are working hard to complete what we see as 1.0-level functionality first. Hopefully that'll happen soon :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:caio.gon...@gmail.com Date:2011-02-28 06:04:59

A SQLite support would be awesome!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:missleig...@gmail.com Date:2011-03-14 15:49:33

Sequel Pro is a marvelous tool. Please make a PostgreSQL version! PostgreSQL tools are so sadly lacking and SP is the best of its kind.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:wojtowic...@gmail.com Date:2011-03-21 03:42:21

+42 for PostgreSQL support! I really miss SP support for my favorite database :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:mspiegel...@gmail.com Date:2011-04-11 15:51:34

I'm moving from MySQL to PostgreSQL and I would very much like to be able to continue using Sequel Pro to manage it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gints.mu...@gmail.com Date:2011-05-06 10:33:40

We are also moving the site from MySQL to PostgreSQL and using sequel pro for it would be fantastic.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:agileapp...@gmail.com Date:2011-05-11 01:46:07

+1 for postgres support

I also love the great looking UI and easy use of sequel pro. it is by far the best database tool for developers I have seen - and I have seen a lot. Postgres Support would be awesome, we are switching everything to postgres right now since the aquisition from oracle.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:andrew.f...@gmail.com Date:2011-05-11 02:37:57

So with all these Postgres votes: any word from the developers yet?
I am willing to donate for PG support!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gints.mu...@gmail.com Date:2011-05-11 04:33:21

They say that development on this "won't start until at least version 1.0 is released". So the question is when 1.0 is planned to release?

@ghost
Contributor

ghost commented Nov 9, 2013

Author:tscha...@googlemail.com Date:2011-06-07 06:24:05

That would be absolutely awesome.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:b...@gratisprint.nl Date:2011-06-22 14:25:11

Some kind of high level roadmapish thing would be nice. Is PostgreSQL still on the radar? 1.1 or 2.0? 1 year or 3 years?

Also: Can I donate or help otherwise?

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2011-06-22 17:55:51

If you want a timeline then plan on it to never happen :)

Really, our focus currently is on making a great MySQL client and when we have accomplished that (which will probably somewhere between 1.2 and 2.0) we will look into other databases.
Implementing support for another dbms (and in general making SP ready for it) is a very very very very time consuming process and there are currently no devs working on this (please keep in mind that we are all volunteers doing this in our spare time!), so for now let's say we will work on it after TextMate 2.0 is released.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:abhibeck...@gmail.com Date:2011-06-22 18:54:30

We absolutely plan to support multiple databases in future, especially SQLite, PostgreSQL.

But right now, everyone is focusing their efforts on improving our MySQL support over support for other databases.

Since nobody has started work on it, it's impossible to put a date/time on it. At this point we have discussed (many times) how support for other databases would be implemented, but that's the extent of it.

If somebody wants to jump in and start working on support for other databases, feel free. Though you will definitely need to a fair amount of experience and free time to throw into the project. We have a lot of MySQL specific code which will need to be re-factored out into some kind of plugin system.

It's a lot of work and nobody has any immediate plans to start on it. As always, it's open source and we welcome new contributors. If you're keen to start on it, this issue is as good a place as any to start discussing how to implement it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:rowanb@gmail.com Date:2011-06-23 03:02:04

It is also worth pointing out that the majority of devs we have at the moment still focus on MySQL as the platform they use at work or for projects. We would appreciate collaborators with a focus on SQLite or PostgreSQL!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:marc...@gmail.com Date:2011-07-20 13:15:50

Just to vote up for SQLite support! Way to go, guys! :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:and.dam...@gmail.com Date:2011-07-20 14:02:30

In order to vote an issue you should just star it using the star icon top-left in the page.

Commenting without any actual contents only pollutes the issue and subscribers by notifying them by email of activity on the issue.

I'm writing this hoping future voters won't comment.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:opti...@gmail.com Date:2011-09-11 16:43:23

Just to follow up, is the move towards QueryKit on trunk code an initial effort for future multi-rdbms support? Can any mainstream dev elaborate on that? Thanks!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2011-09-11 18:52:33

Yes.
That does not mean however that we have any concrete plans for other RDBMses.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2012-01-27 00:42:00

Add my vote for SQLite support. Now that Apple and Rails use it by default, SQLite has become more and more ubiquitous.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:auzigog Date:2012-01-27 16:48:15

I'd love to see PostgreSQL support!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:czar...@gmail.com Date:2012-02-06 07:23:53

+1 for PostgreSQL support.

I have to use Navicat for Postgres and it is HORRIBLE and completely un-intuitive compared to the Sequel Prop UI. PLEASE add Postgres support! I will throw money at you!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2012-02-06 10:25:01

You'd rather throw a Cocoa developer with Postgres experience at us willing to implement it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:octern...@gmail.com Date:2012-03-15 10:23:21

Just as a note, a TextMate 2.0 alpha was released, does that mean that work might have started on this? ;-)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:terinjokes@gmail.com Date:2012-03-15 10:27:03

Per Comment #40, I think we have to wait until TextMate 2.0 is released stable. Just because an alpha has been released doesn't mean that the product itself has been released.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:rowanb@gmail.com Date:2012-03-15 10:30:18

The stage where we start working on this is definitely getting closer. I am surprised that TM2 might actually release beforehand though :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:p...@fabrikbrands.com Date:2012-05-11 02:26:00

SQLite support for me too! Thanks for a superb tool so far.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schmu...@gmail.com Date:2012-05-19 06:16:26

I posted a message on the google mailing list but it seems to be dead, so here I am !

SequelPro is a really great tool (that said the other mysql frontend are so bad...) and I would love to see Postgresql support added as well, actually I wanted to try postgresql for a long time now but there is simply no real client out there which is sad and I just can't use a database without a proper client...

To provide more motivation how about trying to raise donations specifically for this ? I would clearly consider donating for postgresql support.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2012-05-19 07:55:31

The only way we could realise this with donations is if we can pay a developer full-time for a period of 6 to 12 months which would only for 6 months means 62'000€ to 87'000€

I don't think we could raise this amount - and even then we have not yet found anyone proficient enough in ObjC to understand the Sequel Pro code AND be willing to implement postgres.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2012-05-19 08:38:27

Ok, so no Postgresql support would be forthcoming, how about Sqlite 3. Is that still in the cards?

@ghost
Contributor

ghost commented Nov 9, 2013

Author:jrc1...@gmail.com Date:2012-05-19 08:54:22

@max Did you guys ever consider starting something like a Kickstarter campaign to raise the necessary funds? Finding a single sponsor which can come up with a €90k donation would be tough, but crowd funding might be an option. I've no idea how many users are interested in Postgres support, but from the activity in this thread, I think quite a lot. The exposure might also trigger corporate sponsors (maybe a Postgres only platform like Heroku?) to participate. Just thinking out loud here.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:jjlharri...@gmail.com Date:2012-05-19 09:45:31

I would back a Kickstarter campaign for Postgres (or Oracle as I have to use it at work).

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2012-05-19 09:47:56

Getting money is step 2.
Step 1 is finding a developer who could do the job.

The only one we did ever find ran away screaming and started his own database client ;)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schmu...@gmail.com Date:2012-05-21 01:36:24

what is the database client he created ?:)
(I am not linked to it in any way but I read good things about http://menial.co.uk/software/base/ as an sqlite client)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2012-05-22 11:53:00

http://inductionapp.com/

@ghost
Contributor

ghost commented Nov 9, 2013

Author:philfreo Date:2012-05-22 12:09:55

I think a Kickstarter campaign could do really well. Yes you need a developer, but with enough money you can attract good developers to free up their time.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:d...@lobraico.com Date:2012-05-24 01:44:53

I'm not sure if you are actively looking for developers who'd like to help, but I know a bit about the sqlite internals and C/C++ API and would be willing to try to start an effort for sqlite integration if the codebase is anywhere near ready for it.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2012-05-24 02:16:40

Speaking of money, I would gladly pay for Sqlite3 support.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2012-05-24 02:48:16

sorry devzone, what is the link supposed to mean, that there won't be any Sqlite3 support any time soon?

I was referring to support inside of Sequel Pro.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gui.vini...@gmail.com Date:2012-06-08 05:22:56

I certainly would spend some money in a kickstarter campaign.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:Timothy.Heckman Date:2012-06-09 22:00:05

Not to simply +1 the bug report, but I would also be down for a kickstarter campaign.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:j...@318.com Date:2012-06-14 15:05:17

Hoping for PostgreSQL support but I see similar requests have been here for over 3 years so... I'm guessing it's never going to happen.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gints.mu...@gmail.com Date:2012-06-14 15:33:49

I am watching this thread for over a year now and I have a similar feeling. I would also spend money to see postgresql support in sequel pro.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2012-06-15 10:49:22

It took Mozilla 10 years and 12 days to fix a MAJOR bug in Firefox.
We are a much smaller team and this is an enhancement request.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:cid.den...@gmail.com Date:2012-08-24 13:32:36

I would also love to see postgres support. I also pay for the upgrade to have postgres support.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:google-a...@familienservice.de Date:2012-08-30 01:22:32

Maybe you could make a Kickstarter (http://www.kickstarter.com/) for implementing support for multiple database systems (MySQL, PosgreSQL, SQLite) on Sequel Pro, I would definitely pay for it! Since I have no experience in OS X application development, I am not able to support you in another way.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:jrc1...@gmail.com Date:2012-09-03 12:38:40

Good news, everyone: http://stuconnolly.com/blog/sequel-pro-postgresql-support/

@ghost
Contributor

ghost commented Nov 9, 2013

Author:a...@schomb.org Date:2012-09-03 13:03:07

Indeed good news. Thanks for the link!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:officed...@gmail.com Date:2013-05-10 13:40:44

Any updates to this? 1.0 is out :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2013-05-10 13:49:00

Textmate 2.0 is still in Alpha though ;)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:somek...@gmail.com Date:2013-05-10 23:00:31

I don't know if Textmate 2 is still tagged Alpha. but I am using it for a year and half already and it works very well. I don't know what's the relation though.

Sequel-Pro is also very awesome. and PostgreSQL support would be much appreciated.

thank you

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2013-05-10 23:28:45

Textmate 2.0 is still i Alpha, true, but at least it came out (against all odds)!

And that's the reason we all went to SublimeText.

:)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:terinjokes@gmail.com Date:2013-05-10 23:30:31

Nonetheless, has anyone actually bought SublimeText?

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kasperha...@gmail.com Date:2013-05-11 00:06:13

I bought SublimeText.

About PostgreSQL support, that part haven't been touched in the sourcecode since january. Don't seem to get much attention.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:kaku...@gmail.com Date:2013-05-12 01:00:48

I'd say everyone who was using Textmate has seen the light and now bought SublimeText, including me.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:Felix.Bu...@gmail.com Date:2013-05-12 14:27:56

Or switched to MacVim, but could we keep this discussion on topic?

@ghost
Contributor

ghost commented Nov 9, 2013

Author:jimgr...@gmail.com Date:2013-05-12 23:51:54

I just voted for this issue, but wanted to say that the reason for my vote is for PostgreSQL support in particular. I'm about to switch jobs from working with MySQL, where I have loved using Sequel Pro, to working with PostgreSQL. I will greatly miss Sequel Pro :(, but I hope for not toooooo long!

@ghost
Contributor

ghost commented Nov 9, 2013

Author:officed...@gmail.com Date:2013-06-07 09:02:10

> Textmate 2.0 is still in Alpha though ;)

But Sequel Pro is out of Alpha and into 1.0.2 ;) But all jokes aside, why not start a Kickstarter for it? I'd be more than happy to participate for such a thing.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:gui.vini...@gmail.com Date:2013-06-07 10:24:28

Kickstarter campaign!!!

I really think if you guys start one, it's going to be a success.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:schlabbe...@gmail.com Date:2013-06-07 12:06:11

The problems with Kickstarter have already been discussed above.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:officed...@gmail.com Date:2013-06-07 15:50:37

A ctrl + f "Kickstarter" doesn't show any discussion about it, could you link to the discussion about why it can't work please? :)

@ghost
Contributor

ghost commented Nov 9, 2013

Author:t...@timheckman.net Date:2013-06-13 21:11:58

Boy, people are absolutely terrible at following conversations:

https://code.google.com/p/sequel-pro/issues/detail?id=362#c62

Here is explained why a kickstarter won't work.

@ghost
Contributor

ghost commented Nov 9, 2013

Author:jab...@gmail.com Date:2013-06-20 15:03:50

i would pay for postgresql support

@ghost
Contributor

ghost commented Nov 9, 2013

@ghost
Contributor

ghost commented Nov 9, 2013

Author:t...@timheckman.net Date:2013-09-01 11:25:03

Not entirely related to this issue, but as best I can tell PGcommander is half-baked at best. Definitely not a replacement.

Sequel Pro is much more full featured (SSH tunnels, better UX experience, less convoluted interface, etc.)

Nice to have this on github now. \o/

what's the progress on this?

theckman commented Jan 7, 2014

From my understanding there is no progress. This is not something they can, or are willing, to do in their current capacity. There is no developer bandwidth available to implement this.

I don't think this will ever become a feature within SequelPro unless someone becomes the champion and does the implementation themselves.

This is based off of the previous comments I've read. I have no internal knowledge beyond what has been said in the comments from the issue originally on Google Code.

Too bad there's no good alternative to Sequel Pro for other RDBMS:s 👎

Sequel Pro is an awesome SQL client, for what is turning out to be an awful RDBMS: http://grimoire.ca/mysql/choose-something-else#data-processing

spanitz commented Feb 26, 2014

+1 for SQLite support

tslater commented Mar 3, 2014

+1

jopotts commented Mar 4, 2014

An open plea to the main project devs including @stuconnolly (current main developer) & others..

Thank you for building the nicest DB client for the Mac. We all massively appreciate it and [many] are more than willing to pay to support the project. I paid for Navicat for Postgres but it's a constant pain in my dev experience. If I could use Sequel Pro for Postgres then life would be sweet again.

Start a Kickstarter. See what happens. Go on. https://www.kickstarter.com/start Save us all! Please!!

Owner

abhibeckert commented Mar 4, 2014

It's simple, somebody simply needs to start spending their nights/weekends working on it.

There is a small amount of work going on, @stuconnolly made this commit to our PostgresKit a month ago: 065aa16

But it's extremely slow because everyone who contributes regularly to Sequel Pro is using MySQL as our primary database. I myself would be more likely to work on SQLite than Postgres because, while I agree Postgress is one of the best databases available today the reality is the I only use MySQL/SQLite in daily work (and I spend a thousand times more time in MySQL than SQLite).

Instead of trying to pay people to write code how about find a bunch of people willing to do actual work? The move to github makes outside contributions much easier and was the primary driver for our decision to move to github.

I contributed many months of time early on to get Sequel Pro to do the things I personally needed it to do, and now it does all those things and my time is mostly spent on other projects now. Other people have since done the same as me, putting huge amounts of time into the things they needed to see. Somebody (or several somebodies) needs to do the same if we are ever going to see Postrgres in the near future.

Contact @stuconnolly if you want to work on it, he's the best person to tell you what the current status is.

  • Abhi (project founder of Sequel Pro)

a-b commented Mar 5, 2014

Maybe https://github.com/Induction/Induction developers can share some Postgress expertise?

a-b commented Mar 5, 2014

Or opposite ;)

I’d happily pay money to see this happen.

Owner

abhibeckert commented Mar 5, 2014

@a-b induction has the same open source license as us, so there's no reason why code couldn't be shared between both projects.

theckman commented Mar 5, 2014

I doubt the code could be simply shared without much work. I know the limitations here, and I know people would happily fund this. But there is no developer who is willing to do it, nor has the knowledge of the code base to be efficient at doing it... (or so I can tell).

We won't see this until someone gets so fed up with the current Postgres tools that they feel the need to implement it themselves in Sequel Pro.

It's a good piece of software, and I can be hopeful for support one day...

+1 for PostgresSQL supoort

tslater commented Jul 16, 2014

+1 for sqlite

shaneog commented Jul 28, 2014

👍 for PostgresSQL

wavded commented Aug 13, 2014

PostgreSQL would be excellent.

To sum it all up so others don't have to read the entire thread to this point:

1. It's not coming anytime soon

  • Postgres support likely will not be added anytime soon because there's not an available Objective-C developer well versed in Postgres and knowledgeable of the Sequel Pro codebase
  • A Kickstarter campaign is unlikely without first finding such an ideal person (and funding such a person to forego the opportunity cost of their current ventures would likely be prohibitively expensive)
  • The main contributor, @stuconnolly, began the first steps for Postgres support by defining the PostgresKit framework, but it is not being actively developed (and its dependency, PGClientKit, appears abandoned since Nov 21, 2013)
  • Postgres will not be a priority until Sequel Pro is considered a robust, full-featured MySQL client (even though it is already the best available for Mac OS X)

2. Your current alternatives on Mac OS X are

Listed in my order of preference:

PSequel was released recently:
http://www.psequel.com/

Design for Yosemite. Written in Swift. PSequel provides a clean and simple interface to perform common PostgreSQL tasks quickly.

image

Contributor

jbrooksuk commented Dec 2, 2014

+1 for SQLite. I'd happily donate a few $ for it :)

ringods commented Dec 4, 2014

As a developer, I bought myself a license of IntellijJ Ultimate Edition. The Ultimate Edition gives you access to all other JetBrains products (RubyMine, PyCharm, ...) as plugins in the IntelliJ IDE. On top of that, you complete database access to:

  • DB2
  • Derby
  • H2
  • HSQLDB
  • MySQL
  • Oracle
  • PostgreSQL
  • SQL Server
  • SQLite
  • Sybase

It's the by far the only commercial product that I can recommend.

sun4sun commented Jan 31, 2015

Thanks for awesome tool!
I have a little spare time, but a bit of knowledges in Objective-C, C/C++, developing for desktop too. Can writing stuff for Web, before is PHP, now Ruby (overall more half a decade), actually like a continue learning, looking for mentor, any collected or helpful information. Interest in implementation Postgres (SQLite too ) in Sequel. Possible take some parts or ideas from pgAdmin? (both tools are C based)
thanks again

I wonder if @stuconnolly would be interested in continuing his work now that PGClientKit is back alive again, maybe @djthorpe would like to help?

Member

dmoagx commented Mar 1, 2015

@ahti (see #1260 for the question):

Sequel Pro doesn't separate Model and UI very well, meaning, right now the UI code is pretty close to the SQL generation and both is pretty much specific to MySQL.
So the hard part (and probably why this issue hasn't seen much activity) is not to add support for a new RDBMS, but to design an interface layer (OOP, not UI) and refactor MySQL out of the core.

That is pretty much a mammoth task and right now it is missing an agenda we could work along.

The basic application model right now:

  Sequel Pro        SQL statement generation 
      |              and query handling, UI
      v
SPMySQL.framework   C/ObjC API bridge
      |
      v
 libmysqlclient     C-Level MySQL API

What we need:

  Sequel Pro        UI handling
      |
      v
     ???            SQL statement generation
      |              and query processing,
      |              DBMS feature information API
      v
SPMySQL.framework   C/ObjC API bridge
      |
      v
 libmysqlclient     C-Level MySQL API

Personally I still believe it is a bad idea to make Sequel Pro multi-RDBMS.
The definition of "schema" alone is a totally different thing between MySQL, Oracle and MSSQL.
All three require a totally different approach to this stuff, which in the end means either not supporting any RDBMS particularly well or moving so much code (including UI) into different submodules that Sequel Pro would be pretty much an empty shell.

halilim commented Mar 1, 2015

@dmoagx what do you think about PostgreSQL? It's pretty close to MySQL (though I don't know the bounds of the context you define closeness in terms of Sequel Pro architecture). I'd venture to guess many people would be happy to have a MySQL and PostgreSQL only Sequel Pro.

Member

dmoagx commented Mar 1, 2015

I don't have any experience with Postgres, so I can't answer that.

Here's an example though:
MySQL "database": == schema. The object containing tables, views, stored procs, …
Oracle "database": == server instance. Each server instance can have multiple schemas.
MSSQL "database": == container for schemas within a server instance. Each instance can have many databases and each database can have many schemas.

MySQL "user": Unique via (username + connecting host), managed on server instance level.
Oracle "user": == schema.
MSSQL "user": Permissions applied to a "login" on the db level. Logins are managed on the server instance level.

jopotts commented Mar 1, 2015

A Postgres only fork gets my vote. Strip it right back to the bare essentials just to get the project off the ground. I'm guessing that all most of us really want is the nice query editor and results table. All the rest is a bonus.

ahti commented Mar 1, 2015

Looking at @dmoagx example (and I am sure there are many other subtle and not so subtle differences) a potential layer to abstract all those differences away looks like it can't possibly be worth the effort.

So let's take a step back here, and think about why we want SequelPro to support other SQL-implementations (in my case that is SQLite):

  • having a consistent interface: I switch between server-side and client-side development quite often, and thus from MySQL to SQLite. I'd love to view/query/edit both in a consistent interface
  • having a nice interface: imho, SequelPro does a very good job displaying table schemat, contents and query results. While that seems like a minor thing (just use a table and slap everything in there, right?) I have seen other editors do it horribly wrong.

Now, this is only me, and I am not a heavy user nor expert in MySQL and SQLite, so ymmv.

But what I think may apply to other users is that the wish to have SequelPro support other SQLs is mainly due to the great UI.

So what if, instead of jamming all backends into one application, we approach the problem from the other direction: Take the important UI components like the table contents, query editor, schema view, search bar, ... and abstract them to a point where they get their data, and information about nomenclature, possible data types, lists of tables and fields (for the query editor), etc, ... from delegates/data sources.

These components could make the job of implementing a decent database viewer/editor for other backends much easier. SequelPro would still not support other backends, but if someone wants a SQLite version, he doesn't have to spend time making sure the major UI components work great, but can focus on providing data to those components, and building additional UI that is specific to SQLite.

djthorpe commented Mar 2, 2015

I just wanted to comment since I was added into this conversation, and as the author of PostgresKit ( https://github.com/djthorpe/postgresql-kit )...at a cursory glance, looks like there would be some work in order to abstract the code so SequelPro can work with other database servers, and I am focussed at the moment in trying to get V1 out of my framework! There are other alternatives for PostgreSQL (ie, https://eggerapps.at/postico/) which appear to be good.

jwg2s commented Apr 14, 2015

Would also love to see SequelPro support Postgres! I used SequelPro for ~2 years before having to switch to Postico (also a great app, but not quite as robust as SequelPro). 👍

how is the status of the postgres integration? Would love to help, but I have no idea of this programming language... So I just can wait :(

On Wed, Jun 10, 2015 at 10:54 AM, lichtamberg notifications@github.com
wrote:

how is the status of the postgres integration? Would love to help, but I
have no idea of this programming language... So I just can wait :(

@lichtamberg:
Judging from the history of this discussion, it's not likely to happen.
You're better off just finding a decent PG-focused app.

Brandon Zylstra
brandon.zylstra@gmail.com

Owner

abhibeckert commented Jun 11, 2015

@brandondrew if it "wasn't likely to happen" we would have closed this issue or at least set the priority to low.

Work has already begun on Postgres integration. But it's a large undertaking and everybody on the team chooses what and when they work on things, so progress can be slow on anything that's not a serious bug.

Good work sequelpro. I love you. Your work is IMMENSELY appreciated and I've been loving it for 7+ years. Thank you. PG integration does seem to be a huge undertaking especially at the quality that SequelPro operates at. So thanks for the update @abhibeckert

I keep hearing that PostgreSQL is more solid than MySQL
and I have an idea that I should move. However, I don't move
solely because SequelPro is so good, and development would
be much more difficult without it. For me, the perceived benefits
of PostgreSQL are smaller than the benefits of being able to
use SequelPro during development.

If SequelPro supported PostgreSQL, I would consider moving
to PostgreSQL.

bassu commented Jul 1, 2015

@ross-williams There is an indirect alternative with some smart autocompletion that even SequelPro lacks at the moment. For data visualization induction is the best. Ever heard of pgcli ?

noma4i commented Oct 1, 2015

Any progress so far?

It would be awesome to have PostgreSQL and SQLITE support in SequelPro.

You can use http://www.psequel.com to manage PostgreSQL database for the moment.

I love SequelPRO!
I look forward for support of PostgreSQL!

Thank you, awesome team of SequelPRO!

abhibeckert added this to the 2.0 milestone Mar 1, 2016

Owner

abhibeckert commented Mar 1, 2016

This might happen as part of Sequel Pro 2.0. The roadmap for which is maintained here: https://github.com/sequelpro/sequelpro/wiki/Release-2.0

👍

Also, is it possible to add the possibility to choose which columns you want to show/hide in the GUI? This will increase the performance of the NSTableView when you have a lot of data.

Owner

abhibeckert commented Mar 2, 2016

@RomainLanz it's not possible but the next version is likely to handle large amounts of data better

Good to read that! 👍

Thanks for your awesome work.

Member

dmoagx commented May 18, 2016 edited

This is an issue tracker and not a discussion forum.

All comments that do not add value to the issue at hand will be removed.

dmoagx locked and limited conversation to collaborators May 18, 2016

dmoagx unlocked this conversation May 23, 2016

I'm extremely interested in this feature and would be willing to start a bounty on it at https://www.bountysource.com/. Does that seem like a good idea?

Owner

abhibeckert commented Jun 21, 2016

@harrislapiroff please just make a donation via http://sequelpro.com/donate - the money does go towards development.

Having multiple sources of donation creates a ton of extra work on my end that would otherwise be spent actually working on Postgres. You can find a high level overview of our roadmap here: https://github.com/sequelpro/sequelpro/wiki/Release-2.0.

Okay, noted!

Member

dmoagx commented Jun 24, 2016 edited

Kickstarter and co. have been discussed in the past:
#362 (comment)

I still think my estimate is plausible and going by the donations we have received since back then it will take us a few more decades until we have that amount.

Owner

abhibeckert commented Jun 24, 2016

I expect to have an experimental build supporting postrgres some time this year.

gajus commented Oct 31, 2016

Has anyone been working on oracledb support?

@abhibeckert How are things going on this feature? Are there ways any of us can help? Is there a branch we can look at or contribute to?

@abhibeckert Any updates on the Postgres progress? Definitely the main feature I'm looking forward to seeing.

Owner

abhibeckert commented Feb 17, 2017

@miketwalker not much progress to report sorry.

abhibeckert added to Under Consideration in Sequel Pro 2.0 Mar 14, 2017

dmoagx referenced this issue Mar 27, 2017

Closed

Accept donations / bounties #2746

0 of 3 tasks complete

abhibeckert removed this from the 2.0 milestone Mar 27, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment