New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQ] Multiple RDBMS support #362
Comments
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 |
Author:vincent....@gmail.com Date:2010-02-08 15:14:37 would love to see postgres support |
Author:rowan.h...@gmail.com Date:2010-02-25 19:52:00 PostgreSQL Support would be absolutely fantastic |
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 |
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 There are alternatives out there, but their prices are geared to the Enterprise, who's looking for same clients Okay, back to coding! :) |
Author:netsin...@gmail.com Date:2010-05-20 02:49:03 Postgres + Sequel Pro = happy. |
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 |
Author:dhenne...@gmail.com Date:2010-06-24 08:00:05 +1 for this feature. MySQL is starting to smell like Oracle... |
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! |
Author:escarr...@gmail.com Date:2010-07-06 06:34:04 SQLite3 support would be super! |
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. |
Author:mich...@lawler.id.au Date:2010-08-09 22:29:32 Would love to see support for Postgres |
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. |
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. |
Author:mcsno...@gmail.com Date:2010-10-14 07:38:59 postgresql support would be most valuable to me, followed by sqlite |
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. |
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. |
Author:brax...@braxtonbeyer.com Date:2010-11-05 08:02:36 except that you cant use InnoDB |
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 :) |
Author:caio.gon...@gmail.com Date:2011-02-28 06:04:59 A SQLite support would be awesome! |
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. |
Author:wojtowic...@gmail.com Date:2011-03-21 03:42:21 +42 for PostgreSQL support! I really miss SP support for my favorite database :) |
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. |
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. |
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. |
Author:andrew.f...@gmail.com Date:2011-05-11 02:37:57 So with all these Postgres votes: any word from the developers yet? |
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? |
Author:tscha...@googlemail.com Date:2011-06-07 06:24:05 That would be absolutely awesome. |
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? |
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. |
@miketwalker not much progress to report sorry. |
Is this no longer on the table? |
@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. |
What is the status of this? Is there any estimation on when (if ever) Postgres will be supported? |
At this point, I'm willing to pay for PG support in sequelpro. No other software comes close to matching it. |
Postico is a quite good psql app if you are looking for a replacement for sequel pro in the meantime. |
I’m using Valentina Studio, took a while to get used to but it’s ok.
Cheers,
Eric
… On 14 Nov 2018, at 09:50, João Ferreira ***@***.***> wrote:
At this point, I'm willing to pay for PG support in sequelpro. No other software comes close to matching it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#362 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAblCp_RkcEsbdprQaGkAM2naUiyepxZks5uu9lhgaJpZM4BMCsN>.
|
Surely someone has forked this and added the postgres support. |
This probably won't happen ever, TablePlus is quite good, or even DataGrip from jetbrains does it's work. |
It's amazing how fast, easy and intuitive Sequel Pro is. Those other tools are functional but they kind of take time to get used to. With Sequel Pro I'm running queries/analysis in seconds! Love it. |
Why not just add OBDC support?, most databases support it. |
@karimhm please read through the issue before commenting. Nothing at all is added. |
This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I'd still love to see this implemented... |
@tylerbenson please read #3705 - Sequel Pro has been abandoned for a long time. |
Please read about the future in new topic - #3705 Please open new Issue in new repo if you are interested in this feature. |
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.
The text was updated successfully, but these errors were encountered: