I first found Vienna yeeears ago. Used it in a few companies as I usually ran Linux and Vienna was quick and easy to run.
Now I have my own startup and am always plauged with a db client. I do all my development now on a Mac Powerbook and we've settled on using Postgres. So it makes sense to obviously go with a Java SQL client. I assume we'll add developers in the future who might want Linux, so Java will be the way to go. The Postgres PgAdmin tool does not yet support OS X either.
That said, I feel like I've tried every sql client out there and am still not satisfied for one reason or another.
The big two are:
SquirrelSQL: Feels too bloated, kinda quirky, and almost too many choices and too much going on.
DbVisualizer: REALLY bloated feeling, altho I am a big fan of their in-cell editing and theirs is prob the most polished of the Java clients out there. Not sure tho if I wanna fork out $100 for it tho for one user.
And the above (as well as others I've tested) all have too much junk cluttering up the screen. Too many buttons and icons and notification boxes and whatever else. By the time I get a SQL tab in DbVis open, I have too little SQL room and too little results room - THIS is where I really like Vienna.
So, I downloaded the source and made my first micro change: flipped the SQL and results boxes and now I'm thinking of the following:
1. I want the schema browser incorporated on the left side, in a closeable box - or at least an option to have that
2. I would like to get rid of the icon bar all together - or, again an option
3. I want to have highlighted SQL execution instead of the whole SQL box
4. Maybe some more customization like hot keys, setting class path (this has to be a biggie) for drivers, etc.
4a. Also, in schema brwser, a check for INDEX type in view menu.
If I had those four+ things I'd be set (I can live w/out in-cell editing). So my question is, is this something that would go into this project or can I just fork the code into something else? I know forking is an issue in the community and other projects and don't mean it out of disrespect - Mike has built a great tool that helped me work for quite some time. However, it doesn't really look like the project is going anywhere anymore, so that's the only reason I ask.
Well, if I don't hear back, I'll assume that a fork is ok and will post back some info. Thanks.
Jason
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, if anyone reads this.
I first found Vienna yeeears ago. Used it in a few companies as I usually ran Linux and Vienna was quick and easy to run.
Now I have my own startup and am always plauged with a db client. I do all my development now on a Mac Powerbook and we've settled on using Postgres. So it makes sense to obviously go with a Java SQL client. I assume we'll add developers in the future who might want Linux, so Java will be the way to go. The Postgres PgAdmin tool does not yet support OS X either.
That said, I feel like I've tried every sql client out there and am still not satisfied for one reason or another.
The big two are:
SquirrelSQL: Feels too bloated, kinda quirky, and almost too many choices and too much going on.
DbVisualizer: REALLY bloated feeling, altho I am a big fan of their in-cell editing and theirs is prob the most polished of the Java clients out there. Not sure tho if I wanna fork out $100 for it tho for one user.
And the above (as well as others I've tested) all have too much junk cluttering up the screen. Too many buttons and icons and notification boxes and whatever else. By the time I get a SQL tab in DbVis open, I have too little SQL room and too little results room - THIS is where I really like Vienna.
So, I downloaded the source and made my first micro change: flipped the SQL and results boxes and now I'm thinking of the following:
1. I want the schema browser incorporated on the left side, in a closeable box - or at least an option to have that
2. I would like to get rid of the icon bar all together - or, again an option
3. I want to have highlighted SQL execution instead of the whole SQL box
4. Maybe some more customization like hot keys, setting class path (this has to be a biggie) for drivers, etc.
4a. Also, in schema brwser, a check for INDEX type in view menu.
If I had those four+ things I'd be set (I can live w/out in-cell editing). So my question is, is this something that would go into this project or can I just fork the code into something else? I know forking is an issue in the community and other projects and don't mean it out of disrespect - Mike has built a great tool that helped me work for quite some time. However, it doesn't really look like the project is going anywhere anymore, so that's the only reason I ask.
Well, if I don't hear back, I'll assume that a fork is ok and will post back some info. Thanks.
Jason