Live data from Hacker News

Show HN: 10 Years to Build a Free SQL Editor

timestored.com

61–70 of 101 posts

Re: Show HN: 10 Years to Build a Free SQL Editor

#61
FYI, it is kind of ridiculous that you support all these RDBMS but it doesn't mention anything other than DuckDB on the landing page. Your GitHub README is infinitely more useful. You should probably fix that, because the LP gives a very incorrect impression of the capabilities and features of your product!

Edit: just tried it on Windows and you have mojibaked text on the welcome dialog [0].

[0]: https://imgur.com/a/qeIdLGN

Edit 2: Unfortunately your product has some architectural/design issues. Way too much latency, UI hangs a lot simply following the action links in the welcome dialog, trying to open a 3 mib database hung the software until I killed it, etc. The interface is highly non-idiomatic and doesn't follow ui patterns common to any of the major desktops (in response to keyboard shortcuts, mouse operations, etc), and doesn't do a lot of what I would consider to be basic safety/sanity checks (i.e. tries to open a binary database as a text sql file, shows garbled unicode).

Re: Show HN: 10 Years to Build a Free SQL Editor

#62

Congrats on launching! I haven't gotten very far into it, but here's a little feedback about what it took to get to the point where I could try it out. 1. I'm running MacOS 14.4.1. 2. I downloaded the jar file. 3. I double-clicked the jar file. It wouldn't open. I've seen this before, so I navigated to the jar file, right-clicked it and chose open, and it gave me the option to launch it even though it was unsigned af…

Massive thanks for this. I've opened an issue to ensure I improve this: https://github.com/timeseries/qstudio/issues/54 To be honest I've delayed improving Mac as I don't use the platform myself so I don't know how people usually install java apps on mac. I guess it's time I dove in and properly solved this. With the upcoming windows spyware I may have to move platform anyway.

Re: Show HN: 10 Years to Build a Free SQL Editor

#63

I have a genuine question, intended in good faith: why? Why spend 10 years working on this, only to give it way for free?

I originally built it for myself to use with one niche database that had no IDE support at all. I then gave it to my team and then others. Years ago I began to sell it and I still have large banks and finance firms that pay to use it with that one database. Adding support for other databases was actually very little effort however I don't want to have to do the much harder work of: a) Marketing to those users. b) Competing with excellent paid alternatives. c) The various hassle of support / payment processing for many smaller firms. So the large finance firms pay me for the one niche database supported, everyone else gets it free but "unsupported". If a major bank that pays emails a problem, I may have to log in even from holiday to fix it. I'm not doing that for the free users :)

Re: Show HN: 10 Years to Build a Free SQL Editor

#64
post #11

I have a genuine question, intended in good faith: why? Why spend 10 years working on this, only to give it way for free?

They look to be setup as a consultancy. While the title is not wrong it reads different when you realized the parent company has been around for 10years and they list 330+active clients with 850+ projects done.

Woops. Definitely not a consultancy. We make and sell software. The graphic I think you seen had been on the page for years as it came as part of the website template. I had mentally just been blocking it out without realising. I've now removed it.

Re: Show HN: 10 Years to Build a Free SQL Editor

#65

FYI, it is kind of ridiculous that you support all these RDBMS but it doesn't mention anything other than DuckDB on the landing page. Your GitHub README is infinitely more useful. You should probably fix that, because the LP gives a very incorrect impression of the capabilities and features of your product! Edit: just tried it on Windows and you have mojibaked text on the welcome dialog [0]. [0]: https://imgur.com/a/…

Thanks. I've opened an issue to fix the text https://github.com/timeseries/qstudio/issues/55. The binary file issue should definitely be fixed in 3.04+

>>The interface is highly non-idiomatic Ouch this hurts but I'm open to improving it. Have you any specific suggestions?

Re: Show HN: 10 Years to Build a Free SQL Editor

#66
post #16

Apache 2 license that requires email registration. I don't think such a thing exists.

I don't think open source means what you think it does. https://github.com/timeseries/qstudio/tree/master

I intentionally have avoided saying "open source" as it's not yet. Please let me know where it says it, as I may have made a mistake. I just haven't seen enough demand from current or potential users to justify the effort. If you feel strongly on this, please leave a comment here to help justify the effort: https://github.com/timeseries/qstudio/issues/43

Re: Show HN: 10 Years to Build a Free SQL Editor

#67

FYI, it is kind of ridiculous that you support all these RDBMS but it doesn't mention anything other than DuckDB on the landing page. Your GitHub README is infinitely more useful. You should probably fix that, because the LP gives a very incorrect impression of the capabilities and features of your product! Edit: just tried it on Windows and you have mojibaked text on the welcome dialog [0]. [0]: https://imgur.com/a/…

[deleted]

Re: Show HN: 10 Years to Build a Free SQL Editor

#68
post #17

Is it possible to quickly see trends (line graph) for a query result.. If I want to see count of orders over time to see if there are any outliers for potential data issues. That'd be neat. or esp if AI can just check the data... if i have average of 100 orders per day but there is one day that has just 5, I'd want to see that easily.

Yes. All charts render directly from queries. It sounds like you want either time-series or step-plot.

Re: Show HN: 10 Years to Build a Free SQL Editor

#69

Looks cool. What is the benefit of registering? I skipped it to try it out. Was very quick looking at my local MySql database. I liked being able to run sql against some local parquet files. Would need to support Redshift via an ssh tunnel for me to use it on a regular basis. I don't want to manage the tunnel with a different tool.

I think SSH tunnels are exactly the type of thing that should be handled by a different tool. It's a lot of complexity to add to the app, when the app (and any DB client) inherently already supports connecting via an externally managed tunnel. An established tunnel managing program, or just your terminal, would be better at managing tunnels than a tunnel tool tacked onto this app, and the interoperability is already…

No reason why you couldn’t call the ssh binary if it’s available in $PATH. I’ve seen other tools do this too.

You’d need to be transparent in your GUI wording that this is forking SSH (in the case of Windows users) but it wouldn’t be an issue for Linux or macOS.

Re: Show HN: 10 Years to Build a Free SQL Editor

#70
post #21

The messaging is quite confusing. The title makes it seem like it took you ten years to release a first version, but the website says it’s version 3.0 and claims it’s “the leading SQL Editor […]”¹. There is a GitHub repo² but the history is quite unhelpful, with a bunch of commits named the same and some older commits after newer ones. ¹ Unless it were the only one, it would be impossible to be leading right after la…

The story is: I made a big push to open source it a few years ago but none of my users seemed to care. They mostly cared it's Free. Doing the boring work of getting the build working on github etc. doesn't seem valuable to my users vs adding functonality. I'm open to being wrong so I opened an issue and if anyone comments, I will open source at least one file for each comment: https://github.com/timeseries/qstudio/is…

Seeing this makes me not take you or your project seriously. Bumping commit count and playing some engagement farming game. Either open source or don't.

> Doing the boring work of getting the build working on github etc. doesn't seem valuable to my users vs adding functonality.

You don't need this to open source it, you can provide source without setting up builds

Post reply on HN