https://app.tabbydata.com/sql-assistant-demo
Show HN: Describe SQL using natural language, and execute against real data
1–10 of 37 posts
Re: Show HN: Describe SQL using natural language, and execute against real data
#2Re: Show HN: Describe SQL using natural language, and execute against real data
#3Re: Show HN: Describe SQL using natural language, and execute against real data
#4Would be happy to chat and compare notes if you'd like!
Re: Show HN: Describe SQL using natural language, and execute against real data
#5I thought it was funny in that in the weather dataset that "NULL" comes in first for the win for some questions:
> what is the all time rainiest city? > what are the top 5 most dry states?
The query conversion is impressive!
Re: Show HN: Describe SQL using natural language, and execute against real data
#6At Veezoo (http://www.veezoo.com) we have been tackling this problem for over 5 years now.
Under the hood we are using our own models. With GPT-3 we're a bit worried about the lack of fine-grained control needed for productive use-cases and obv. also lock in.
Will try out against the same dataset and see how it compares!
Re: Show HN: Describe SQL using natural language, and execute against real data
#7We did a similar analysis a while back, works surprisingly well! I OpenAI increases the amount of "training data" you can send in, I think it could get really good at generating SQL. https://blog.seekwell.io/gpt3
Re: Show HN: Describe SQL using natural language, and execute against real data
#8Very nice! I’ve been working on something similar recently: https://acolytehq.com . Would be happy to chat and compare notes if you'd like!
Re: Show HN: Describe SQL using natural language, and execute against real data
#9ie, "ERROR: Syntax error: Expected end of input but got keyword END at [49:3]"
Re: Show HN: Describe SQL using natural language, and execute against real data
#10May be some rough edges - or I have unreasonable expecations. The weather data set has 'begin' and 'end' columns which generates bad sql. ie, "ERROR: Syntax error: Expected end of input but got keyword END at [49:3]"