Oh yeah, last time I checked, Sequel Pro doesn't build in XCode 4.
> benefit of OSS being that you have access
> to the source to fix/add things
The place where this is the most beneficial is when considering businesses looking to invest in a technology. If you invest in a company/software product that goes under, then you could be saddled with a piece of tech that you can't fix bugs for, etc. If it's open source you at least have the chance to do so, even if the community around it collapses and there is no new development.The idea that access to the source is some sort of cure-all is a fallacy, but it may also just be a straw man. I don't know that anyone says that all open source projects are going to be manageable just because the source is available, but they are by definition more manageable than a project with no source available.
http://code.google.com/p/sequel-pro/issues/detail?id=362&...
Developer input from mid-2011 is towards the bottom, but in short the gist is "that would be great, contributions welcome".
If only it were as easy as `gem install pg`.
I would totally throw $20 at a kickstarter to pay someone. That's what, optimistically? Two weeks of work? How quickly could we scrounge up $10k?
Shit. More like $100, now that I think about it.
It is with MacRuby, but that's a whole different set of problems :)
Apple highly encourages using ARC over GC for new development.
Their wording there is suspect though. Interesting - thanks for the link!
I guess you meant latency, where reference counting generally has better latency than incremental garbage collection.
1) Every GUI function results in a SQL log entry so you can learn/improve your SQL if you're not a guru.
2) You can give this to an analyst (whose db user is restricted appropriately) and have them be productive in adding and updating data.
3) Any view can be exported to CSV, so the analyst can use what they know (ie, Excel) to do things you might not care about but are important (ie, pivot tables, etc).
4) It's free.
Compared to every other RDBMS GUI I've used:
It crashes very infrequently. It doesn't randomly slow down whenever I click on something. The settings page is relatively straightforward. There aren't fifteen different windows with different functions. The UI makes sense and is also very straightforward.
So, I was rescuing an MS Access application that imperfectly synched from a MySQL instance powering the Rails app from which it got data, that had been exported to MS SQL that was running (surprisingly well) inside a Windows XP VM I was accessing via Remote Desktop Connection.
So: I have no idea. I totally forget. It was some really-complicated-looking MS tool that allowed me to look at the table row by row and run some queries :). The guy I was working for set it up; my excuse is I stopped using windows back in 2004.
How easy it is to install and maintain. How performant it is. How good are the tools associated with it.
I've yet to run into a situation where MySQL was holding me back. Since the only thing postgres has got going for it, from my standpoint, is that my friends prefer it and it is cooler… I think that until I have a better reason I will stick to the one with the better toolset.
Right now, Sequel Pro is that tool. I use it almost every single day.
Can't someone just add database drivers to Sequel Pro? It's far and away the best Database GUI I've ever used and its reliance on MySQL is actually keeping me from moving to PostgreSQL full time.
(i.e. http://www.sequelpro.com/ and http://www.sequelpro.com/docs/Source_Code - a little crazy they're still on SVN but oh well)