saigal
Re:Show HN: We open sourced our entire text-to-SQL product
on Thursday May 30, 2024 @06:39PM (#40529543)
we intend to
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @06:18PM (#40478256)
The autonomous car analogy is a good one. The technology is overall so far superior to a human (probably scrolling TikTok) driving but the moment it makes a mistake we remove the AEV which would be to to higher societal benefit.
Decisions should be made against an alternative, not against some fictitious perfect solution.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @03:20PM (#40477207)
Couldn’t agree with this more. Exactly.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @01:47PM (#40476598)
For companies that are willing to put in some effort, the self hosting option is a great one. There are certain use cases where this works now, and is already in production. These tend to be use cases with some constraints and don’t deal with very sensitive data.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @11:43AM (#40475693)
we've encountered a lot of instances when people know SQL but just want a first draft of SQL to expedite the process. we see this a lot from data analysts too.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @10:42AM (#40475335)
yes. some want BYOC solutions. others don't want to even be perceived as being used to train an LLM. not to mention CCPA, GDPR, etc etc etc.
lots of questions around what data is being sent to the LLM, or just schema.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:48AM (#40474705)
The question was around row level security
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:48AM (#40474699)
Yes totally agree. You can easily sniff out products that are simple wrap of GPT
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:47AM (#40474691)
Search bar within the SaaS interface that allows user to ask data questions and returns back NL answer or specific cut of data
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:46AM (#40474679)
Yes. Correct.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:45AM (#40474677)
We also encounter a lot of build vs buy conversations with businesses.
Re:Show HN: We open sourced our entire text-to-SQL product
on Saturday May 25, 2024 @08:44AM (#40474667)
Enterprises are spending lots of time and money on this. The biggest issue that has slowed down sales cycle at this stage has been data governance. Most folks think it’s about accuracy or latency (which of course is an issue) but data governance can make this whole thing a non starter.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:30PM (#40472448)
https://discord.com/invite/A59Uxyy2k9
discord invite in case anything comes up
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:27PM (#40472436)
there is a middle ground here. the most complicated queries will need the intel and business context of a smart data scientist. there are however so many types of queries where automation would make the world so much easier and allow more self-serve type data inquiries. too often the rhetoric around these topics is binary as in "it works" or "it doesn't work." in reality, there are certain use cases that work now and others that don't yet.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:24PM (#40472426)
fantastic. let us know how it goes :-)
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:23PM (#40472421)
is there an easier way?
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:21PM (#40472410)
if you expect correct 99% of the time, you will be waiting for a very very very long time for most, except for the most constrained, use cases
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @11:20PM (#40472403)
"...what it expects them to do"
therein lies the nuance. some people expect to get a natural language answer back. others expect to get a data table back. others expect to get correct SQL back. this is why it's so important to understand the use case and not bucket everything together.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @08:09PM (#40471587)
I agree with you. The larger point with text to SQL, however, is that it will not work if it is a simple wrap of an LLM (GPT or otherwise). Text to SQL will only work if there is a sufficient understanding of the business context required. To do this is hard, but with tools such as Dataherald a dev's life gets a whole lot easier.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @07:35PM (#40471413)
Yes please do. We’d love your feedback and or to hear whether you see material improvement over what you have now
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @06:57PM (#40471217)
No
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @06:53PM (#40471198)
allow me to clarify.. Dataherald isn't intended for developers because they don't know SQL, it's intended for developers who want to build text to SQL into their products
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @06:37PM (#40471121)
We’ve seen demand from all types of SaaS applications where the user might need data— software that helps customer support staff answer data questions, CRM, payroll software, just to name a few.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @06:04PM (#40470874)
"Anything more natural requires a lot of context and needs to solve ambiguity.
this is precisely why we created Dataherald-- to make it much easier to add that business context so that NL to SQL could actually be good enough to get into production
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:59PM (#40470838)
while i agree, there is clear demand for people to use natural language to SQL. we have tremendous conviction around the desire for natural language tools, but of course the technology and product need to deliver desired results.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:58PM (#40470829)
i agree that there will be "early adopter" type use cases and others that might take a while (e.g. healthcare with hipaa compliance)
it is still the early days. goal is to give the developer tools to do this easier.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:56PM (#40470815)
hmm not sure I understand the question
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:50PM (#40470779)
Tbh the original intention was to be the "data analyst" but we found over time (and with literally 100s of user conversations at small cos and enterprises) the embedded use case was more interesting and made for a better business, which was not at all what we expected.
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:44PM (#40470734)
"The agent is LLM agnostic and you can use it with OpenAI or self-hosted LLMs."
Re:Show HN: We open sourced our entire text-to-SQL product
on Friday May 24, 2024 @05:15PM (#40470534)
Apache 2.0.