I can't be the only person who was disappointed that this isn't Trello for Beekeepers.
:-)
Show HN: Beekeeper Studio – open-source, cross-platform SQL client
91–100 of 135 posts
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#92Looks great. Sequel Pro you mentioned is by far the best on Mac, none of the clients on Windows or Linux I tried even come close. This is great, and badly needed IMHO—specially if one can use a single app for both MySQL and SQL Server (Beaver DB is a usability nightmare). The name will put off a lot of people. To be honest, if someone in a team said "we should replace all our SQL clients with Beekeeper!" the first re…
Thanks! There's a history to the name, but I agree there are negatives.
The positive is that it is distinct and can hopefully provide its own identity. Businesses use all sorts of software with silly names!
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#93Earlier quoted context omitted.
Good catches! Can you file a GitHub issue so I don't forget?
Not that it's a big thing, but seems weird to put the responsibility about you not forgetting something, on the person leaving the feedback, rather than just filing the issue yourself.
It seems weird that someone who has spent a lot of their own time (e.g. money) to help a community is being shunned for not taking even more time out of their day for a simple request.
This also disregards software ticket guidelines 101:
- There isn't fully defined steps to reproduce
- Limited details on what the user expected to see
- No details about the users environment
People pour their souls into FOSS projects and regularly get cr*pped on for not acting like Enterprise Support. So let's try to be a little more empathetic to people who contribute freely to the dev community, even if its just a small ask like this.
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#94Hey folks, This is a passion project from myself and a friend. Been looking for a slick and easy to use SQL client on Linux for a while (I wanted basically Sequel Pro, on Linux, for PSQL). Couldn't find what I wanted, so we made one ourselves. It's built on Electron using Vue.js - I know HN opinions on electron apps, but I've been surprised on how snappy the app is. It's fully open source (MIT), cross-platform (Linux…
Passion aside, how do you plan to monetize?
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#95Very cool! I’ve been looking for a decent cross-platform SQL client for a while, so I can’t wait to try this out tomorrow. In case anyone is curious, here’s what I’ve tried so far: - DataGrip: bulky, slow, bugs never get fixed, non-FOSS - Azure Data Studio: great interface, but no MySQL or SQLite support - phpMyAdmin: clumsy, lacking in features, requires a web server—I’m really not the target demographic for this on…
I notice you had not tried squirrleSQL
OP's client looks way nicer for sure
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#96Very cool! I’ve been looking for a decent cross-platform SQL client for a while, so I can’t wait to try this out tomorrow. In case anyone is curious, here’s what I’ve tried so far: - DataGrip: bulky, slow, bugs never get fixed, non-FOSS - Azure Data Studio: great interface, but no MySQL or SQLite support - phpMyAdmin: clumsy, lacking in features, requires a web server—I’m really not the target demographic for this on…
TablePlus is my favorite one after trying most of those https://tableplus.com/
Once they publish the docs for how to build plugins, TablePlus is going to be the obvious choice. I can't wait for my database browser to have charting!
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#97Wow, thanks for creating and sharing your work!
Up until now I haven't seen a decent native SQL client on linux.
Since I'm working with vue I will totally check out the source and how you put things togehter :)
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#98Looks nice and I've been looking for a client that works with SQL Server and Postgres for a while now. Giving it a try for sure. Feedback: 1) When I first setup a connection and save it, the modal stays there, should probably be dismissed at that point 2) It wasn't clear how to connect, so I double clicked which worked. Maybe an explicit 'connect' button next to each connection would be nice. 3) I really like how aft…
Wow, great feedback, thanks!
Yeah the data-formatting in the table is something I need to work on, everything is just treated as a string right now, just so I could ship in a reasonable amount of time. That will improve for sure.
Other information for tables will be my next big feature release I think. Probably as a tab-view. Still not figured this out exactly yet.
Thanks for the monitization callout, although I'm committed to keeping all core app features totally free forever. :-)
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#99Earlier quoted context omitted.
Not that it's a big thing, but seems weird to put the responsibility about you not forgetting something, on the person leaving the feedback, rather than just filing the issue yourself.
Oh you just caught me trying to encourage community involvement :-). I don't just want users, I want contributors! At a minimum some issue engagement is very useful.
Heh, was what I thought initially, but didn't want to call out anything! Certainly fine and no hard feelings! Good luck :)
Re: Show HN: Beekeeper Studio – open-source, cross-platform SQL client
#100Earlier quoted context omitted.
Not that it's a big thing, but seems weird to put the responsibility about you not forgetting something, on the person leaving the feedback, rather than just filing the issue yourself.
Well, it's open source, so he volunteers his time. Maybe the feedback should have been filled to Github in the first place? Certainly he is not lazy if asking to do a favor but probably busy with something else.
Sure, but if time is of such importance here, copy+pasting the feedback into a new issue is faster than replying to the author and ask them to file the issue. Then it might be that they don't because of X, so you have to file it yourself anyways.
In both scenarios, just filling the issue yourself is faster