We had a comment in our codebase that said SQL Server doesn't handle pagination well, so we should just avoid pagination for now. And it did exactly that: shipped the entire result set to the browser and let it sort itself out. Same deal for Spanner.
A lot of Basedash is just "run the SQL the user wrote, show the rows." We support 10+ dialects (Postgres, MySQL, BigQuery, Snowflake, Athena, SQL Server, Spanner, and friends), and every query gets paginated because we can't stream a 12M row result set to a browser.
Great idea, more so for the executives.
Natural language to SQL gets a bit tricky when you have a lot of tables and joins; any benchmarks?
Putting the data analyst inside Slack is smart because that’s where the question already happens. The hard part is keeping answers trustworthy. Do replies include the query/source trail behind each chart?
Having data answers show up right inside Slack feels like the right place for this. It saves the usual back-and-forth of opening dashboards, asking an analyst, or chasing a chart later.
Basedash: AI data analyst
@farrukh_butt1 exactly! Some of our users use Basedash exclusively through Slack which is pretty cool.
The promise sounds great but I'm always wondering how these tools handle messy real world data. That's usually where things get interesting
ApyHub : The All in one API Platform
I love products that meet users where they already work, and Slack is definitely where a lot of teams spend their day.
Being able to ask a quick question and get an answer with a chart directly in the thread sounds much more convenient than switching between dashboards and analytics tools.
The scheduled reports and automated insights are a nice touch too, sometimes the most valuable data is the information you didn't think to ask for.
Basedash: AI data analyst
@gabriella_anjani appreciate it, we agree!