81–90 of 147 posts
Earlier quoted context omitted.
As I wrote on the original thread, we recommend using the RDBMS row-level security features. This blog discusses how to do that on Postgres https://www.2ndquadrant.com/en/blog/application-users-vs-row...
Way way too complicated. I thought this tool was suppsed to make my life easier
Thank you! This is exactly something we are look for at querro.io
I still wonder who the audience is for tools like this. The website posits you can answer data questions without going through an analyst, but the role of the analyst is not to be a SQL whisperer for PMs and Executives - it is to be an expert in the model and the data. A data warehouse of any real scale is going to have some amount of issues - anomalous data, different interpretations of the same numbers - how does t…
This is the grievance I have as a data scientist. It is one of the fields where things are technical, while meanwhile everyone thinks they could do the job and provide excessive input and exact direction.
Thank you! This is exactly something we are look for at querro.io
discord invite in case anything comes up
Earlier quoted context omitted.
I agree that is a more reasonable use-case. The readme for this tool seems geared toward the business of answering business questions.
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.
Curious why you decided to open source your entire product. Are you moving to an open core model? I’d expect in that case that much of 2, 3 & 4 would have stayed closed. Would be grateful if you can share your reasoning
At least with that you get 100% accuracy at the expense of having to use a fixed syntax.
Earlier quoted context omitted.
> the target audience is developers who wish to embed text to SQL functionality into their own products Who is asking?
you wouldnt believe the amount of developers that don't know how to write sql
There is no requirement to learn SQL for most of the applications built today.
Never understood why I would want to use this over an NLP+ORM system. At least with that you get 100% accuracy at the expense of having to use a fixed syntax.
How ould the NLP+ORM system do this?