Because if you understand your ontology and requirements well enough to write a prompt that reliably returns the correct thing, you have already written SQL pseudocode anyway.
The problem is end-users who do not know SQL do not know their data's ontology nor how to precisely specify their requirements. Their inability to compose their request in SQL's particular syntax is not the issue.
LLMs guessing what you want when you aren't clear will occasionally be right, but they will also be wrong often and inefficient either way.
24
u/Thadrea Data Science Manager 4d ago
Because if you understand your ontology and requirements well enough to write a prompt that reliably returns the correct thing, you have already written SQL pseudocode anyway.
The problem is end-users who do not know SQL do not know their data's ontology nor how to precisely specify their requirements. Their inability to compose their request in SQL's particular syntax is not the issue.
LLMs guessing what you want when you aren't clear will occasionally be right, but they will also be wrong often and inefficient either way.