Matt Wonlaw

In node / ios / android / desktop this is a non-issue as queries resolve in microseconds.

Workaround is live. Ideally we can remove `@ts-ignore` statements to complete this fix.

Do you have a sense for how much overhead might be added in the vtab conversion of query results? Or how much more complexity would need to be added to...

we've decided to go the function extension route after perf tests against the vtab.

Seems related to your goals -- https://github.com/mycelial/sqlite_wasm

oops, looks like I never actually pushed the changes but only published them to npm. Fixed that. I merged the latest `sql.js` changes in with @jlongster's changes here: https://github.com/tantaman/sql.js/tree/alt-deploy And...

There's a fork of the `sqlite3` package that only coerces integers if the exceed max_safe_int. This is probably a more acceptable fix: https://github.com/juanrgm/node-sqlite3/commit/e25579c683695dc9074b7373452c660342fb6462 better-sqlite3 converts all things to bigint when...

This is the case where multiple nodes should share a common interface and the schema maintainer would like to create an edge to that interface rather than the concrete nodes....

The initial use cases all revolve around: 1. A user sharing data with themselves. 2. A user sharing their data with a subset of other users Trust is high (absolute...

some of these seem to be impossible to model in Typescript. Query types should _always_ be able to have the correct generics as these are user facing. Down a layer...