<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Towards Complex Text-to-SQL in Cross-Domain Database with Intermediate Representation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1905.08205/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1905.08205/feed.xml" rel="self" type="application/rss+xml" /><item><title>Towards Complex Text-to-SQL in Cross-Domain Database with Intermediate Representation — mentioned by qsort</title><link>https://news.ycombinator.com/item?id=35436061</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.08205:35436061</guid><pubDate>Tue, 04 Apr 2023 07:00:12 GMT</pubDate><description>&lt;p&gt;&amp;gt; I’d like to imagine the non technical folks using something like the dashboard example in the article would be ok with some extra work formatting their query to ensure what they think they want, is precisely what they’re asking for. The UX in this area is very much work in progress, but from what I have seen I agree that users likely prefer to be sure that the query is correct. What I would try to do -- and let&amp;#x27;s be clear, this is just a random opinion and my guess is as good as anybody&amp;#x27;s -- is to answer with two results, &amp;quot;this is my interpretation of what you asked&amp;quot; and &amp;quot;this is the answer…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.08205/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
