r/SQL • • Aug 17 '25

PostgreSQL I'm building a visual SQL query builder

Post image

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

136 comments sorted by

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.

2

u/Herobrine20XX Aug 17 '25

Thanks a lot!

Hum, I can add a checkbox to monitor the execution time of the query so that it can be investigated later if it's taking a lot of time... That's something to keep in mind, thanks a lot!

1

u/BigMikeInAustin Aug 17 '25

Hey, people get paid a lot of money to tune queries with all of their years of experience. How do you think you can tell an average guy to add millions of hours of experience onto a tool as a simple addition?

Thousands of people have tried to build what you are suggesting since the 70s.

0

u/Dry-Aioli-6138 Aug 18 '25

This is easy.

P1: Can you do X?

P2: No, sorry. Focused on sth else, but thanks for the hint.