HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
explorerhq
sql-explorer
Python2014–2021
explorerhq / sql-explorer

sql-explorer

SQL reporting that Just Works. Fast, simple, and confusion-free. Write and share queries in a delightful SQL editor, with AI assistance.

6Distinct people
11Mentions
0Explicit recommenders
2.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

SQL reporting that Just Works. Fast, simple, and confusion-free. Write and share queries in a delightful SQL editor, with AI assistance.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:24:10 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2014-01-10 00:48:53 UTC to 2021-05-10 16:14:54 UTC.

01232014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC211
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC321
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

11 sources
At Grove, we are: Airflow -> S3 -> DBT with Spark/EMR or Redshift/Spectrum -> Redshift data marts -> Looker At least, that’s the way we like our pipelines to work. In practice we have a couple of extractions that land directly in Redshift (we extract Zendesk data, for instance, with Stitch Data). We use Snowplow for click stream analytics. And we’ll likely move from Redshift to Snowflake (or mayybbbeee Bigtable) in Q2 of 2020. We used to do all of our transforms via DBT within Redshift but have been offloading the heavier-duty pieces (like Snowplow event processing) to Spark jobs because they were too taxing on Redshift. We’ve gone through 3 “generations” of Looker reporting — gen 1 was just wrapping LookML around our schema and forcing Looker to do the joins and generate SQL for everything we wanted to know. Second generation involved a
Read the rest
bunch of common table expressions within Looker itself that worked, but were developed without much thought as to data mart design. Gen 3 is where we are now with super deliberate scoping and implementation of warehouses in DBT. Before any of that we rolled our own tool [0]. Happy to answer any questions. We’ve gone from ~30 to ~1000 employees in the 3 years since we started using Looker and have learned a thing or two along the way. [0] https://github.com/groveco/django-sql-explorer
In Ask HN: What does your BI stack look like?
I maintain an open source project for writing SQL queries[0] that currently uses codemirror. I find it a little sluggish to load. This looks like it could be a good option -- the one thing that would make it a codemirror killer for me is the ability to resize the editor window; something text areas obviously natively support, but codemirror does not. Any idea if Monaco does? [0] https://github.com/groveco/django-sql-explorer
In The Monaco Code Editor
Looks like a nice tool. I wrote https://github.com/epantry/django-sql-explorer, which is sort-of similar in terms of the problem it solves, except embraces SQL front-and-center. Excited to check this out in more depth. Personally, I think it's really exciting is that this is all written in Clojure! We need more Clojure web apps out there to learn from! An initial glance at the source makes it seem very readable as well. A great learning resources for us amateur Clojurists. Also makes it clear that the ecosystem is pretty immature; there is a lot of frameworky boilerplate to support a straightforward REST API.
In Show HN: Metabase, an open-source business intelligence tool
This looks pretty awesome! It is also worth mentioning Django SQL Explorer (https://github.com/epantry/django-sql-explorer), which has all of the presented features, as well as handy schema definition by the side. It also allows for parameters in the queries, which is very useful (e.g. leaving the timeframe customisable before running a query). With Django 1.8 now being easier to install/deploy to wherever, this is a great plugin to allow more people data access!
In Slinky – An easy way to query your PostgreSQL data
Django SQL Explorer https://github.com/epantry/django-sql-explorer Engineers or analysts write SQL queries, and share them with anyone in the business who needs the data to make decisions. Through over a year of heavy, daily real-world use, I've added dozens of little usability features that make it (for me at least) really pleasant to use. It's still a pretty under-the-radar Django app, but I literally can't imagine life without at, at any business I've ever worked at. Explorer can also expose select queries as read-only pages to specific users and we use this feature to keep investors and partners up to date on key metrics and financials which saves a lot of time and ad-hoc reporting. Just go to a URL and BAM! Real time data, downloadable as CSV. I've also documented the version and license of every dependency to make it as easy as poss
Read the rest
ible for businesses to go ahead and use it. And finally, it's extensively tested via automation, and our own internal deployment which is always running off the tip of master. We dogfood every commit quite heavily.
In Ask HN: Brag about open-source projects you're proud of

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.