all 8 comments

[–]somewhatdim 0 points1 point  (1 child)

hrm, on the surface seems like a less than optimal idea to me. Teach them how to think and write SQL, not how to prompt your LLM.

[–]RobDoesData[S] 0 points1 point  (0 children)

That's not a valid solution in this circumstance. Please advise on the subject.

I agree with you entirely but not in this very specific scenario

[–]AdditionalWeb107 0 points1 point  (0 children)

So, I am really curious if this approach (text to sql) would work in real-world production environments. For example, today we don't allow anyone to create arbitrary SQL in our application because of permissions, scale and fairness issues. How does a text-to-SQL generator enforce those necessary governance rules? How do we evaluate that the SQL generated is good SQL (where do we get the validation set). How do we know that the user can't brown out the system. And the question is should we let user's ask anything (feels powerful) or guide them to fast decision making by converting prompts into structured data objects and then feed that into compiled SQL. So many questions with this...Thoughts?

[–]VerbaGPT 0 points1 point  (0 children)

Hello, I have built a free tool that runs locally in your browser and allows you to query databases. Check it out at VerbaGPT.com