ThanksI did build something similar (although in python and with some other hard requirements).My problem, and seems that your experience it too, is that the users will never know that the query is invalid. They will get a result for sure, but the SQL could be totally wrong.

Does this [1] look like the thing you&#x27;re looking for?We built a basic Re-Act agent that can dynamically inspect the database context and generate the queries iteratively.Our experience was that it was hard to do single-shot.Happy to answer any questions.[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;inferablehq&#x2F;inferable&#x2F;tree&#x2F;main&#x2F;adapters&#x2F;pgsql-adapter">https:&#x2F;&#x2F;github.com&#x2F;inferablehq&#x2F;inferable&#x2F;tree&#x2F;main&#x2F;adapters&#x2F;...</a>

I was tasked with building a &quot;native language interface&quot; to our database. After developing it for a month, it seems to me that I hit a wall with the correctness of the resulting SQL. 80-20 would be a good estimate. My feeling is that it something that cannot be used a regular user.Did you do better and you have tips?NOTE: I&#x27;m not talking about performant queries only about producing a correct result. I would say that only about 50% cannot be better optimized, but I don&#x27;t care about that.

Ask HN: Integrating SQL and LLM what is you experience