ggsql developer here. It's quite fun to see an alternative implementation of our syntax so early. Why did you decide on this path rather than working with the ggsql duckdb extension? (honest curious question - not trying to push you away from your path)
I can only imagine the load you might end up in if you have to keep feature parity with ggsql along with all the other features you have
Looks great!
One minor correction - the `summarize` function in duckdb can also be used in CTEs etc.
But you have to wrap the `summarize` in a `from` clause like this:
Thank you! I'll add note about it
The plotting aspect of this seems very similar to:
https://opensource.posit.co/blog/2026-04-20_ggsql_alpha_rele...
That's exactly the inspiration! I made a post here on HN about that a few weeks ago: https://news.ycombinator.com/item?id=48108815
My plan is to release a blog post about all VISUALIZE current features next week, explicitly mentioning Posit's alpha GGPLOT.
/edit: clarifications
ggsql developer here. It's quite fun to see an alternative implementation of our syntax so early. Why did you decide on this path rather than working with the ggsql duckdb extension? (honest curious question - not trying to push you away from your path)
I can only imagine the load you might end up in if you have to keep feature parity with ggsql along with all the other features you have