71–80 of 85 posts
Earlier quoted context omitted.
> If only it were as easy as `gem install pg`. It is with MacRuby, but that's a whole different set of problems :)
And with GC on the way out in OS X... MacRuby has their work cut out for them.
Earlier quoted context omitted.
I've never used Sequel Pro, but I've used plenty of other RDBMS GUIs. What's so special about Sequel Pro? It certainly doesn't look like anything to write home about (compared to say the MS SQL tools).
I'll take a shot: 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,…
Earlier quoted context omitted.
I've never used Sequel Pro, but I've used plenty of other RDBMS GUIs. What's so special about Sequel Pro? It certainly doesn't look like anything to write home about (compared to say the MS SQL tools).
I can't speak for the MS SQL tools. I used one of them once? and it was extremely lame but I can't comment. 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.
Earlier quoted context omitted.
That's just patently untrue: either GTk or Qt would work perfectly. I don't see why the desktop environment would matter--the program doesn't have to (and probably shouldn't) care whether I'm on Gnome or KDE or Unity. Moreover, all the popular environments support both GTk and Qt fairly well, and both are cross-platform, so you would actually be supporting more users than with a Mac OS-only program. Really, fragmenta…
> Moreover, all the popular environments support both GTk and Qt fairly well, and both are cross-platform, so you would actually be supporting more users than with a Mac OS-only program. By that logic Windows should be first since it has the most users. Also, are you sure that the installed base of Gtk+ or Qt (or both) is greater than the installed base of OS X?
There are also cross-platfrom native options like wxWidgets. These also work both on Linux and other systems.
Finally, the last StackOverflow survey[1], which I think is pretty representative of the sort of people who would use a program like this, had both Linux and OS X at about the same level (~20% each). So Linux is certainly not negligible.
[1]: https://www.surveymonkey.com/sr.aspx?sm=2RYrV_2bFw2aZ2RfedWH...
Earlier quoted context omitted.
And with GC on the way out in OS X... MacRuby has their work cut out for them.
GC is on the way out? I haven't heard that before... have a link?
Apple highly encourages using ARC over GC for new development.
Serious question: 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)
Oh yeah, last time I checked, Sequel Pro doesn't build in XCode 4.
Earlier quoted context omitted.
I can't speak for the MS SQL tools. I used one of them once? and it was extremely lame but I can't comment. 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.
re: MS SQL Server tools and lame - really? The SQL 2000 tools were pretty basic, but since about 2005 they've been pretty good. I'd be interested to hear what you found lame. I guess maybe you were using something else from MS' cornucopia of GUI database tools (a plethora of wizards inside visual studio, access etc).
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.
Serious question: 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)
It's open source, so anyone can add their own db drivers to it. The problem, as with other open source projects, is that the task is not trivial. (I tried to patch Sequel Pro last year) Which is also why I don't buy the oft-quoted benefit of OSS being that you have access to the source to fix/add things. BS. 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 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.
Looks interesting, but there are no binaries and the XCode project didn't compile right away. (I guess, being a software developer, I should go and try to figure out what's breaking the building process. On the other hand, I've never used XCode and don't know enough about OS X library management to figure out broken deps)
Sorry about that! Binaries are up at https://github.com/Induction/Induction/downloads Let me know what build errors you're getting. I would do well to document the requirements (Postgres, Redis)...