Visual SQL builders live or die on the import direction — pasting an existing messy query and seeing it laid out is way more valuable than building from scratch. How robust is the SQL → canvas parsing? That's the feature I'd actually come back for.
visual SQL builders have been around forever, most feel like they were designed by someone who never writes joins, this one has reverse-engineering from existing SQL which is enough to try it
hey guys, I am the creator of the SQLJoiner project. Nice to meet you all :)
Thank you for the feedback.
The project was created to help navigate (understand in my head) large/complex queries done by other people.
To answer your questions:
1. Plans to support other sql flavors?
- SQLite support has been recently implemented
- Maybe in the future, Postgresql.
- Nothing from Microsoft. Sorry, I rarely use Microsoft software.
2. How robust is the SQL → canvas parsing?
- It is basic (draws correctly simple SELECT, WHERE, JOINS). Feature upgrades require manually drawn query contexts (feedback for RE).
5 comments
[ 2.4 ms ] story [ 24.6 ms ] threadThank you for the feedback.
The project was created to help navigate (understand in my head) large/complex queries done by other people.
To answer your questions: 1. Plans to support other sql flavors? - SQLite support has been recently implemented - Maybe in the future, Postgresql. - Nothing from Microsoft. Sorry, I rarely use Microsoft software. 2. How robust is the SQL → canvas parsing? - It is basic (draws correctly simple SELECT, WHERE, JOINS). Feature upgrades require manually drawn query contexts (feedback for RE).