4 ms·
And I should mention this is heavily inspired by Stack Exchange's Data Explorer (which is credited in the readme file). We used an implementation of Data Explor
by numlocked 13y ago
And I should mention this is heavily inspired by Stack Exchange's Data Explorer (which is credited in the readme file). We used an implementation of Data Explorer at my previous company (shout out to HN user moserware who came up with that idea) and it was a fantastic way to quickly share data and answer questions. We would wonder how a particular site metric was performing, and an engineer could quickly post a link to a query in hipchat - and we could talk about real data quickly instead of speculation.
- sendob 13y agowill be taking it for a spin! Another tool, different, but also great for sharing, you may enjoy: http://htsql.org/ http://htsql.org/
- numlocked 13y agoI took a look at this before I undertook building SQL explorer, but it looked like overkill and I didn't want to learn a new query language and introduce a learning curve to every employee who might write queries. But it does look fairly full featured. Have you used it? Is it low-friction enough that people want to use it?
- sendob 13y agoI have used it. Adoption was good especially for simple queries, people were less focused on the language, and more focused on exploring/modifying examples. For people who are already familiar with SQL and as you said, less interested in the query language, it may be almost immediately frustrating. I can absolutely see circumstances where it would be overkill, I have never tried to use it as a performance critical tool, just as more an easy thing to slap on to ease access, two aspects that I have found useful on more than one occasion: 1. HTRAF toolkit is convenient for very basic visualization (depending upon the audience this can be very useful to have at hand quickly) 2. multiple output formats (json in particular) has been helpful in terms of quickly hacking together prototypes in the past