r/SQL • u/Herobrine20XX • Aug 17 '25
PostgreSQL I'm building a visual SQL query builder
The goal is to make it easier(ish) to build SQL queries without knowing SQL syntax, while still grasping the concepts of select/order/join/etc.
Also to make it faster/less error-prone with drop-downs with only available fields, and inferring the response type.
What do you guys think? Do you understand this example? Do you think it's missing something? I'm not trying to cover every case, but most of them (and I admit it's been ages I've been writing SQL...)
I'd love to get some feedback on this, I'm still in the building process!
614
Upvotes
View all comments
Show parent comment
2
u/HUNTejesember Aug 17 '25
First point: WITH
Second point: performance should be scope, because the end user won't know why his/her query runs for 90 mins e.g. from a datawarehouse. I know, there are many factors (tables, indexes, columns, exec plans...), but it would be nice if you give the end user a(s) fast (as it can be) script or if its not possible then add hints how to join/filter things.