"What is the price of Ginger Beer?"<p>It couldn't translate that into SQL.<p>"What is the price in dollars of Ginger Beer?"<p>> SELECT Catalog_Contents.price_in_dollars FROM Catalog_Contents WHERE Catalog_Contents.price_in_dollars = "Ginger Beer"<p>Nope.<p>"What is the price in dollars of catalog entry name Ginger Beer?"<p>> SELECT Catalog_Contents.price_in_dollars FROM Catalog_Contents WHERE Catalog_Contents.catalog_entry_name = "Ginger Beer"<p>Cool! You have to be more specific than I was hoping, but this is still pretty neat.
There’s a lot missing here. During the brief and unhappy period of my life where I worked in this area, we had quite a lot of luck just generating semantics based on Wordnet in the domain in question. So here you can’t successfully ask for “French wines” even though we know what a country is and that French is a correct adjectival form. Same with things like “oldest wine”, that’s an easy to derive superlative based on info you already have. We got some mileage out of this old fashioned tree based system at the core, with fuzzier machine learning stuff at the edges.
> What singer sang in the most stadiums?<p><pre><code> SELECT singer.Name FROM singer JOIN singer_in_concert ON singer.Singer_ID = singer_in_concert.Singer_ID GROUP BY singer.Singer_ID ORDER BY COUNT(*) DESC LIMIT 1
</code></pre>
It is close... sort of? It figured out it needed to join, group, and order, but it only drew the relation to the concert, not the venue. Correctness seems a huge challenge here. Even knowing SQL, I feel I'm double checking my results at times. But I can see how this might be incredibly useful someday for Salesforce if there's confidence in the results.
> how many teachers older than thirty?<p>> SELECT COUNT(*) FROM teacher WHERE teacher.Age > "thirty"<p>Not a bad idea. A good idea, maybe. Implementation needs some work.
The Covid database contains cumulative figures, so if you ask "How many deaths in ...?" you get the naive query with the sum of the Deaths column for that country, which is wrong. Actually I wonder how to explain it. I cheated and asked "how many deaths in ... on July 14?" but got the wrong query, with July 14 as Province_or_State no matter how I rephrased the date.
In my opinion this doesn't make sense.<p>SQL is a tight, unambiguous language, that's why it exists.<p>This is like a legal document written in spoken English. It's only all fine when it works.<p>Part of writing SQL is also understanding the underling data. This won't address this issue.<p>This is also not replicable. Language changes in context and time.
see also <a href="https://news.ycombinator.com/item?id=24283687" rel="nofollow">https://news.ycombinator.com/item?id=24283687</a>
list all company<p>> Please check the results in the table. Did I get it right?<p>yes<p>> Great!<p>list all designation<p>> Sorry, 'designation' is confusing to me