[REQ] Multiple RDBMS support

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by brandon....@gmail.com on 8 Aug 2009 at 3:10

[GoogleCodeExporter]

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.

Original comment by stuart02 on 20 Aug 2009 at 6:53

• Changed state: Accepted
• Added labels: Component-Logic, Milestone-Release1.0, Priority-Medium, Usability

[GoogleCodeExporter]

Original comment by stuart02 on 16 Oct 2009 at 8:43

• Added labels: Milestone-Release1.1
• Removed labels: Milestone-Release1.0

[GoogleCodeExporter]

Original comment by stuart02 on 16 Nov 2009 at 2:40

• Changed title: [REQ] Multiple RDBMS support

[GoogleCodeExporter]

would love to see postgres support

Original comment by vincent....@gmail.com on 8 Feb 2010 at 11:14

[GoogleCodeExporter]

PostgreSQL Support would be absolutely fantastic

Original comment by rowan.h...@gmail.com on 26 Feb 2010 at 3:52

[GoogleCodeExporter]

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.

Original comment by mjpta...@gmail.com on 10 Mar 2010 at 10:28

[GoogleCodeExporter]

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

Original comment by levi...@gmail.com on 4 Apr 2010 at 4:51

[GoogleCodeExporter]

Postgres + Sequel Pro = happy.

Original comment by netsin...@gmail.com on 20 May 2010 at 9:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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.

Original comment by andrew.f...@gmail.com on 20 May 2010 at 10:00

[GoogleCodeExporter]

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

Original comment by dhenne...@gmail.com on 24 Jun 2010 at 3:00

[GoogleCodeExporter]

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!

Original comment by coldcac...@gmail.com on 2 Jul 2010 at 6:47

[GoogleCodeExporter]

SQLite3 support would be super!

Original comment by escarr...@gmail.com on 6 Jul 2010 at 1:34

[GoogleCodeExporter]

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

Original comment by vermyn...@gmail.com on 20 Jul 2010 at 7:32

[GoogleCodeExporter]

Would love to see support for Postgres

Original comment by mich...@lawler.id.au on 10 Aug 2010 at 5:29

[GoogleCodeExporter]

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.

Original comment by and.dam...@gmail.com on 10 Aug 2010 at 9:29

[GoogleCodeExporter]

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.

Original comment by gene...@gmail.com on 16 Aug 2010 at 9:07

[GoogleCodeExporter]

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

Original comment by mcsno...@gmail.com on 14 Oct 2010 at 2:38

[GoogleCodeExporter]

Issue 871 has been merged into this issue.

Original comment by stuart02 on 22 Oct 2010 at 12:20

[GoogleCodeExporter]

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.

Original comment by lailso...@gmail.com on 4 Nov 2010 at 2:47

[GoogleCodeExporter]

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.

Original comment by 4braham on 5 Nov 2010 at 5:28

[GoogleCodeExporter]

except that you cant use InnoDB

Original comment by brax...@braxtonbeyer.com on 5 Nov 2010 at 3:02

[GoogleCodeExporter]

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

Original comment by rowanb@gmail.com on 5 Nov 2010 at 3:17

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Issue 951 has been merged into this issue.

Original comment by stuart02 on 18 Jan 2011 at 6:54

[GoogleCodeExporter]

A SQLite support would be awesome!

Original comment by caio.gon...@gmail.com on 28 Feb 2011 at 2:04

[GoogleCodeExporter]

Issue 994 has been merged into this issue.

Original comment by stuart02 on 5 Mar 2011 at 5:44

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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.  

Original comment by missleig...@gmail.com on 14 Mar 2011 at 10:49

[GoogleCodeExporter]

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

Original comment by wojtowic...@gmail.com on 21 Mar 2011 at 10:42

[GoogleCodeExporter]

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

Original comment by mspiegel...@gmail.com on 11 Apr 2011 at 10:51

[GoogleCodeExporter]

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

Original comment by gints.mu...@gmail.com on 6 May 2011 at 5:33

[GoogleCodeExporter]

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

Original comment by agileapp...@gmail.com on 11 May 2011 at 8:46

[GoogleCodeExporter]

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

Original comment by andrew.f...@gmail.com on 11 May 2011 at 9:37

[GoogleCodeExporter]

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?

Original comment by gints.mu...@gmail.com on 11 May 2011 at 11:33

[GoogleCodeExporter]

Issue 1052 has been merged into this issue.

Original comment by stuart02 on 14 May 2011 at 4:04

[GoogleCodeExporter]

That would be absolutely awesome.

Original comment by tscha...@googlemail.com on 7 Jun 2011 at 1:24

[GoogleCodeExporter]

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?

Original comment by b...@gratisprint.nl on 22 Jun 2011 at 9:25

[GoogleCodeExporter]

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.

Original comment by schlabbe...@gmail.com on 23 Jun 2011 at 12:55

[GoogleCodeExporter]

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.

Original comment by abhibeck...@gmail.com on 23 Jun 2011 at 1:54

[GoogleCodeExporter]

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!

Original comment by rowanb@gmail.com on 23 Jun 2011 at 10:02

[GoogleCodeExporter]

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

Original comment by marc...@gmail.com on 20 Jul 2011 at 8:15

[GoogleCodeExporter]

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.

Original comment by and.dam...@gmail.com on 20 Jul 2011 at 9:02

[GoogleCodeExporter]

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!

Original comment by opti...@gmail.com on 11 Sep 2011 at 11:43

[GoogleCodeExporter]

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

Original comment by schlabbe...@gmail.com on 12 Sep 2011 at 1:52

[GoogleCodeExporter]

Original comment by stuart02 on 13 Jan 2012 at 11:38

• Removed labels: Milestone-Release1.1

[GoogleCodeExporter]

Issue 1260 has been merged into this issue.

Original comment by stuart02 on 14 Jan 2012 at 10:53

[GoogleCodeExporter]

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

Original comment by kaku...@gmail.com on 27 Jan 2012 at 8:42

[GoogleCodeExporter]

I'd love to see PostgreSQL support!

Original comment by auzigog on 28 Jan 2012 at 12:48