Any solutions like this that work with self hosted models?
Depends what you mean by 'work.' You can definitely use them, but GPT-4 is the only model that generates good SQL without lots of training + fine-tuning (and it is very difficult/impossible to come up with Nl SQL training sets). So GPT-4 is the only model that works well in terms of accuracy for now. That being said, I am pretty sure the self hosted models will get there very soon. Are you looking to deploy a solutio…
Show HN: Dataherald AI – Natural Language to SQL Engine
51–60 of 108 posts
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#52Will definitely look at using Dataherald for adding proper SQL support!
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#53Nice job! We're building something relatively similar at Vanna AI: https://vanna.ai/
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#54Very nice! I added a similar feature to https://sitespeak.ai recently that allows my users to connect their virtual assistant to a Sqlite database to retrieve data to answer visitor questions. Initially this was just a way around the difficulty of "chatting to a CSV" so the solution was to convert any CSV to a Sqlite database and using that, but it's proved very useful. Will definitely look at using Dataherald for ad…
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#55DO NOT make any DML statements (INSERT, UPDATE, DELETE, DROP etc.) to the database.
I've found that spelling out exactly what I don't want an LLM to do dramatically increases the probability that it will do exactly that.
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#56Congrats on the initial launch! Here a few thoughts, feedback, and questions: * you do a good job in this post of describing why you need more than just ChatGPT to get acceptable quality, but much less of that is in the readme. I wouldn't be afraid to sell the project a bit harder, even in early days * likewise, I think a small visual of the architecture would be helpful, just to make clear what the relationship is t…
You can connect the hosted version to your data warehouse using the SQLAlchemy connectors which are in the open source engine, and the connection info will be stored after being encrypted. An on-prem version of the enterprise product is also on the roadmap.
For protecting against errors the approach is to allow for a human to be in the loop as you alluded to. One of the core pieces of the engine is the Evaluation module which combines white box and black box techniques. You can block the response from going back to the question asker if the confidence level is below a certain threshold until a human verifies the response manually (or always put the human from the data team in the loop).
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#57Congrats on the initial launch! Here a few thoughts, feedback, and questions: * you do a good job in this post of describing why you need more than just ChatGPT to get acceptable quality, but much less of that is in the readme. I wouldn't be afraid to sell the project a bit harder, even in early days * likewise, I think a small visual of the architecture would be helpful, just to make clear what the relationship is t…
Thanks for the feedback regarding the Readme. We have some additional detail in the docs here https://dataherald.readthedocs.io/en/latest/index.html (including an architecture doc), but will definitely be incorporating some of the feedback as we iterate on the documentation which. You can connect the hosted version to your data warehouse using the SQLAlchemy connectors which are in the open source engine, and the con…
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#58Nice job! We're building something relatively similar at Vanna AI: https://vanna.ai/
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#59From the prompt context: DO NOT make any DML statements (INSERT, UPDATE, DELETE, DROP etc.) to the database. I've found that spelling out exactly what I don't want an LLM to do dramatically increases the probability that it will do exactly that.
Re: Show HN: Dataherald AI – Natural Language to SQL Engine
#60From the prompt context: DO NOT make any DML statements (INSERT, UPDATE, DELETE, DROP etc.) to the database. I've found that spelling out exactly what I don't want an LLM to do dramatically increases the probability that it will do exactly that.
Yeah, I hope this is paired with something that actually stops those statements from running otherwise this is a pretty naive way to do this.