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.
Basedash: AI data analyst
Honestly
Congrats on the launch! What are the most common datasources Basedash for Slackuses for analysis? Relevant data lives across multiple platforms for most companies so curious on about what you and the team have seen so far
This looks like a massive time-saver for answering ad-hoc executive questions! Since it's translating natural language to query real data sources, how does Basedash handle complex or messy database schemas to ensure it doesn't pull the wrong metrics or hallucinate an answer?