[REQ] Multiple RDBMS support #362

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

Comments

@ghost
Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

would love to see postgres support

Collaborator

ghost commented Nov 9, 2013

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

would love to see postgres support

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

PostgreSQL Support would be absolutely fantastic

Collaborator

ghost commented Nov 9, 2013

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

PostgreSQL Support would be absolutely fantastic

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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! :)

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

Postgres + Sequel Pro = happy.

Collaborator

ghost commented Nov 9, 2013

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

Postgres + Sequel Pro = happy.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

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

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

SQLite3 support would be super!

Collaborator

ghost commented Nov 9, 2013

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

SQLite3 support would be super!

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

Would love to see support for Postgres

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

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

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

except that you cant use InnoDB

Collaborator

ghost commented Nov 9, 2013

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

except that you cant use InnoDB

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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 :)

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

A SQLite support would be awesome!

Collaborator

ghost commented Nov 9, 2013

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

A SQLite support would be awesome!

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

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

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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?

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

That would be absolutely awesome.

Collaborator

ghost commented Nov 9, 2013

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

That would be absolutely awesome.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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?

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

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

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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

I'd love to see PostgreSQL support!

Collaborator

ghost commented Nov 9, 2013

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

I'd love to see PostgreSQL support!

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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!

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Nov 9, 2013

Collaborator

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.

Collaborator

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.

@djthorpe

This comment has been minimized.

Show comment
Hide comment
@djthorpe

djthorpe 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.

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

This comment has been minimized.

Show comment
Hide comment
@jwg2s

jwg2s 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). 👍

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). 👍

@lichtamberg

This comment has been minimized.

Show comment
Hide comment
@lichtamberg

lichtamberg Jun 10, 2015

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 :(

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 :(

@brandondrew

This comment has been minimized.

Show comment
Hide comment
@brandondrew

brandondrew Jun 10, 2015

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

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

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Jun 11, 2015

Member

@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.

Member

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.

@alexparker

This comment has been minimized.

Show comment
Hide comment
@alexparker

alexparker Jun 16, 2015

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

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

@ross-williams

This comment has been minimized.

Show comment
Hide comment
@ross-williams

ross-williams Jun 17, 2015

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.

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

This comment has been minimized.

Show comment
Hide comment
@bassu

bassu 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 ?

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

This comment has been minimized.

Show comment
Hide comment
@noma4i

noma4i Oct 1, 2015

Any progress so far?

noma4i commented Oct 1, 2015

Any progress so far?

@RomainLanz

This comment has been minimized.

Show comment
Hide comment
@RomainLanz

RomainLanz Oct 27, 2015

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.

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.

@ysmolsky

This comment has been minimized.

Show comment
Hide comment
@ysmolsky

ysmolsky Jan 27, 2016

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

Thank you, awesome team of SequelPRO!

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

Thank you, awesome team of SequelPRO!

@abhibeckert abhibeckert added this to the 2.0 milestone Mar 1, 2016

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Mar 1, 2016

Member

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

Member

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

@RomainLanz

This comment has been minimized.

Show comment
Hide comment
@RomainLanz

RomainLanz Mar 2, 2016

👍

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.

👍

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.

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Mar 2, 2016

Member

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

Member

abhibeckert commented Mar 2, 2016

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

@RomainLanz

This comment has been minimized.

Show comment
Hide comment
@RomainLanz

RomainLanz Mar 2, 2016

Good to read that! 👍

Thanks for your awesome work.

Good to read that! 👍

Thanks for your awesome work.

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx May 18, 2016

Member

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.

Member

dmoagx commented May 18, 2016

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 dmoagx locked and limited conversation to collaborators May 18, 2016

@dmoagx dmoagx unlocked this conversation May 23, 2016

@harrislapiroff

This comment has been minimized.

Show comment
Hide comment
@harrislapiroff

harrislapiroff Jun 21, 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?

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?

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Jun 21, 2016

Member

@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.

Member

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.

@harrislapiroff

This comment has been minimized.

Show comment
Hide comment

Okay, noted!

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Jun 24, 2016

Member

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.

Member

dmoagx commented Jun 24, 2016

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.

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Jun 24, 2016

Member

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

Member

abhibeckert commented Jun 24, 2016

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

@gajus

This comment has been minimized.

Show comment
Hide comment
@gajus

gajus Oct 31, 2016

Has anyone been working on oracledb support?

gajus commented Oct 31, 2016

Has anyone been working on oracledb support?

@harrislapiroff

This comment has been minimized.

Show comment
Hide comment
@harrislapiroff

harrislapiroff Nov 3, 2016

@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 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?

@miketwalker

This comment has been minimized.

Show comment
Hide comment
@miketwalker

miketwalker Feb 17, 2017

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

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

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Feb 17, 2017

Member

@miketwalker not much progress to report sorry.

Member

abhibeckert commented Feb 17, 2017

@miketwalker not much progress to report sorry.

@abhibeckert abhibeckert added this to Under Consideration in Sequel Pro (next feature release) Mar 14, 2017

@dmoagx dmoagx referenced this issue Mar 27, 2017

Closed

Accept donations / bounties #2746

0 of 3 tasks complete

@abhibeckert abhibeckert removed this from the 2.0 milestone Mar 27, 2017

@affanshahid

This comment has been minimized.

Show comment
Hide comment
@affanshahid

affanshahid Aug 12, 2017

Is this no longer on the table?

Is this no longer on the table?

@abhibeckert

This comment has been minimized.

Show comment
Hide comment
@abhibeckert

abhibeckert Aug 13, 2017

Member

@affanshahid I'm currently working on changes that are a pre-requisit to this.

I removed the milestone tag a few months ago because we've stopped using milestones and are now using projects.

Member

abhibeckert commented Aug 13, 2017

@affanshahid I'm currently working on changes that are a pre-requisit to this.

I removed the milestone tag a few months ago because we've stopped using milestones and are now using projects.

@abdulrahman-khankan

This comment has been minimized.

Show comment
Hide comment
@abdulrahman-khankan

abdulrahman-khankan Apr 17, 2018

What is the status of this? Is there any estimation on when (if ever) Postgres will be supported?
Is it contributions problem? i.e. will more contributions/donations help or it's more lack of resources (maintainers)?
Thanks!

abdulrahman-khankan commented Apr 17, 2018

What is the status of this? Is there any estimation on when (if ever) Postgres will be supported?
Is it contributions problem? i.e. will more contributions/donations help or it's more lack of resources (maintainers)?
Thanks!

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