Even though SQL is generated behind the scenes, if a query run fails to execute, no SQL is returned to the frontend.
That's not optimal:
- doesn't give a chance for users to correct the query
- user doesn't see what's going on
- slows down the response time quite a bit (specially with remote DB connections that are already super slow), we could be returning SQL a lot sooner
I think we should think about the 'remove result' pattern again @anthony2261
RamiAwar / dataline
Chat with your data - AI data analysis and visualization on CSV, Postgres, MySQL, Snowflake, SQLite...
830
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too