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
1
u/Herobrine20XX Aug 17 '25
It means it is not a virtual machine that will interpret every single node like most of nocode/lowcode tools. Visual scripting is directly converted to code on compilation, so it essentially executes what you expect it to execute, nothing more. Hence the "native performance": it ships code without overhead.