perspective VS chdb

Why do you want to render to canvas?

Perspective seems to be the most performant html table. It is more focused on extremely fast updates than styling, although it looks good.

Glide is a newcomer that also renders to canvas.

https://github.com/finos/perspective

https://github.com/glideapps/glide-data-grid

SQL workbench also uses https://perspective.finos.org/ for tables. It's a WASM table library which pairs nicely with duckdb and works well with large tables.

Yes. We are working on adding support for aggregation and pivoting using https://github.com/finos/perspective

I haven't looked extensively at react-datasheet. It looks like it is trying to build more of a full product than the other data tables.

I have used ag-grid extensively, its an impressive product. Some pieces are a little awkward to use, particularly auto-sizing. But generally ag-grid has thought of most functionality and has a solution. The creator of ag-grid had a great interview on Javascript Jabber [1].

The other serious data table component that I have seen is FinOS Perspective [2]. This is extremely high performance, also more specialized and probably harder to customize. I think Perspective renders to a canvas element from Rust/C++ compiled to WASM (not 100% sure). It is also made for streaming updates.

AG-Grid supports streaming updates... but only in the commercial version.

Eventually the data model for these types of tables becomes tricky. I will be investigating parquet-wasm for my use case. Hit me up if you want to collaborate.

[1] https://blog.ag-grid.com/javascript-jabber-podcast/

[2] https://perspective.finos.org/

Something like https://github.com/finos/perspective ? We use an OLAP(-y) WASM engine to provide query-ability to our data visualization tool, and doing the calculations in the browser is cheaper and simpler than a server-side database for datasets that fit in browser memory.

Hey HN, creator of DB Pilot here.

I first announced DB Pilot on HN back in April: https://news.ycombinator.com/item?id=35761979.

Since then a lot has improved: More databases are supported, most of the product can now be used for free, and most importantly:

The app now comes with an analytics workspace powered by an embedded ClickHouse instance, running locally on your machine. This allows you to query local files, files on S3, PostgreSQL, SQLite & more - and all of those at once.

Embedding ClickHouse was possible thanks to chDB (https://github.com/chdb-io/chdb). A recent discussion on HN about it: https://news.ycombinator.com/item?id=37985005

I recommend using ClickHouse instead of DuckDB.

It has been around since 2016, and it covers and extends the feature set of DuckDB with a huge margin. Worth noting that it never has breaking changes in its table format MergeTree.

I'm tracking the progress of DuckDB and see that it is modeled after ClickHouse, but does not approach it in terms of feature completeness, stability, or performance.

The closest to DuckDB option is to use its self-contained version, clickhouse-local: https://clickhouse.com/blog/extracting-converting-querying-l... or an embedded version, chdb: https://github.com/chdb-io/chdb

Different beasts, but if by any chance you love ClickHouse already and just want to run OLAP queries in-process, there's chdb: https://github.com/chdb-io/chdb

> Can you embed it in Python as a library?

https://github.com/chdb-io/chdb

    pip install chdb

New kid on the block that I prefer over DuckDB is CHDB (https://github.com/chdb-io/chdb). Embedded ClickHouse, so once you out grow your laptop you can simply move to an actual OLAP that's Open-source.