Just wanted to say thank you for all your effort on SQLExplorer, I incorporated it into our open source radiotherapy quality assurance project (https://qatrackplus.com) years ago and it's been a great addition and is used in hospitals around the world :)
That's amazing! Thanks so much for sharing. Happy to chat if there are specific features or functionality that would be useful. Always looking for more feedback.
But I didn't know until I read your comment here about the uploading CSV, instant parsing that non technical people may find very interesting. This is something pgweb for example doesn't have.
Your docs are also missing a complete sample env.
See that you've integrated pivottable. Nice touch!
If you can figure out minimal barcharts , you may even have an opensearch/log community interested.
Another killer idea is uploading CSV/json and getting faceted search.
No one does this! But maybe distracting to your roadmap.
I think GP is referring to something like excel’s filters, where the UI exposes filter options dynamically based on the data actually available after all existing filters have been applied.
It’s absolutely open source - and completely free for commercial use. That license simply encumbers that specific functionality from resale. I don’t want anyone selling a SaaS version for profit (if someone wants to do that, they can contact me and we can talk about it).
Awesome project. But a somewhat irrelevant suggestion. OP could have shared the video via YouTube for better user experience (adaptive bitrate streaming) and also not had to worry about paying for S3.
Great job! And congrats on actually getting something out there. I can really see this being useful for some organizations.
I also envisioned this same type of tool around 10 years ago and it is still on my ever growing list of ideas to implement. I took the idea further to support not only SQL but other languages such as HTML, JavaScript, Python, C#, etc. You could then support returning different types of media based on the URL extension such as .html to return a webpage, .json to return a JSON API, .csv to return a CSV file, etc. As time marched on, many of these same ideas came to fruition in things like AWS Lambda, Jupiter Notebooks, Microsoft Monaco Editor, etc.
This is awesome, I hope I get a chance to use it once.
One thought: I think the effort should be put into the UI for the non-technical end users, instead of query builders/developer experience. I would be even fine with a tool doesn't even have a query tool and just executes SQL files from a folder/git repo. The important part would be for me to provide a perfect experience for the end users. Developers usually have a lot of tools at hand to create queries, no need for another one.
Yep - that makes sense. The Query pane can be collapsed, effectively hiding the SQL from the end user. This is indeed how a number of people use Explorer. But it could certainly be more optimized, in the direction you suggested. I'll think about how this might be improved!
I like the simplicity, and yet there is a lot of stuff to do.
I know there are bunch of tools that do this (superset, redash, dbeaver web etc.) but there is a great value in the feature and UX choices of any particular tool.
Great effort! Feels like you should be charging for this, maybe a Pro Plan with SSO (user edits integrated into your history logs) and 1 year support for SMEs to self-host.
Nope - but would love to do it. At the moment you can clone the repo and run start.sh which should work but obviously is not bulletproof like a docker image. Feedback and PRs welcome!
That's a very harsh comment to give someone that has poured hours of their life into something trying to help others unpaid. You could at least politely ask what makes it different than redash.
Perhaps a bit impolite, but no offense taken. It's a very crowded space and there are a ton of good tools! I work on SQL Explorer simply because I get to make the thing that works best for me.
Redash is very focused on visualization. SQL Explorer is not. It is going more in the direction of in-browser analysis.
Otherwise, I‘m very open to feedback, just create an issue in the linked GH Repo. Thanks!
See https://tobilg.com/using-duckdb-wasm-for-in-browser-data-eng...
Excellent effort overall.
But I didn't know until I read your comment here about the uploading CSV, instant parsing that non technical people may find very interesting. This is something pgweb for example doesn't have.
Your docs are also missing a complete sample env.
See that you've integrated pivottable. Nice touch!
If you can figure out minimal barcharts , you may even have an opensearch/log community interested.
Another killer idea is uploading CSV/json and getting faceted search. No one does this! But maybe distracting to your roadmap.
Keep up the excellent work!
Good luck!
But I like some of the features in SQL Explorer interesting - like Pivot tables and exposing queries as JSON endpoints.
Not really open source. If you care about that.
But saying it's open source when its license does not follow OSI's definition is confusing at best, or misleading at worst.
OSI doesn't have a monopoly on the term, but that's the generally accepted definition (at least IME).
The "upload csv file" box does not show up in the test project.
https://github.com/explorerhq/django-sql-explorer/blob/64170...
It should be in the docs, but I'll make sure it's more prominent!Any reporting tool is only as good as the data available to it.
I built Multiwoven, a Reverse ETL with SQL capabilities, to sync data from any data warehouse to destinations like this one.
https://github.com/Multiwoven/multiwoven
I also envisioned this same type of tool around 10 years ago and it is still on my ever growing list of ideas to implement. I took the idea further to support not only SQL but other languages such as HTML, JavaScript, Python, C#, etc. You could then support returning different types of media based on the URL extension such as .html to return a webpage, .json to return a JSON API, .csv to return a CSV file, etc. As time marched on, many of these same ideas came to fruition in things like AWS Lambda, Jupiter Notebooks, Microsoft Monaco Editor, etc.
One thought: I think the effort should be put into the UI for the non-technical end users, instead of query builders/developer experience. I would be even fine with a tool doesn't even have a query tool and just executes SQL files from a folder/git repo. The important part would be for me to provide a perfect experience for the end users. Developers usually have a lot of tools at hand to create queries, no need for another one.
I would use a tool like that as a low-code platform to quickly make data accessible. Might be a different use case than most users are looking for.
I know there are bunch of tools that do this (superset, redash, dbeaver web etc.) but there is a great value in the feature and UX choices of any particular tool.
Keep it up m8.
And it can do PDF export (with a plugin).
Would love to hear what you have in mind?
Redash is very focused on visualization. SQL Explorer is not. It is going more in the direction of in-browser analysis.