Statistics that live in your SQL

 (kolistat.com)

64 points | by caerbannogwhite 1 day ago

3 comments

  • PashaGo 10 minutes ago
    Interesting, but I think it works only for quick ad-hoc analysis. For dashboards or deeper research, you still need other tools
    [-]
    • caerbannogwhite 2 minutes ago
      Yes, that's exactly its main purpose! I initially started because I needed a dataset browser. I work with clinical trials, so we usually get raw data files in all possible formats, from CSV to EXCEL and, of course, SAS formats. But since I was already using DuckDB, I thought about extending it a bit further, so you can quickly get a glance at the data.
  • williamcotton 1 hour ago
    The plotting aspect of this seems very similar to:

    https://opensource.posit.co/blog/2026-04-20_ggsql_alpha_rele...

    [-]
    • caerbannogwhite 1 hour ago
      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

      [-]
      • thomasp85 1 hour ago
        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

        [-]
  • geysersam 39 minutes ago
    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:

      with
    some_table as (from range(10)),
    x as (from (summarize some_table))
  from x;
    [-]