datasette-graphql VS madatdata

Impressive how little code is involved here! This is really neat.

The biggest feature I can see that's missing is pagination - it looks like this doesn't have a way to retrieve e.g. ten results, then pass a next token to get back the next set.

Here's how I implemented pagination in my similar datasette-graphql plugin (which also gives you a GraphQL API for an existing SQLite database): https://github.com/simonw/datasette-graphql#pagination

My source code is here, but it likely won't be much use to you - it's full of weird introspection because I'm trying to make this work against any database table: https://github.com/simonw/datasette-graphql/blob/1.4/datasette_graphql/utils.py

You might like what we're building with Seafowl [0], which is an open-source, single binary database you can deploy to the edge for executing cache-friendly queries (so e.g. you can deploy to fly.io free tier, load your data into it, and put Cloudflare in front of it to cache query results like any other HTTP response).

Here's an example [1] multi-page site with Next.js and Seafowl.

[0] https://seafowl.io/docs/getting-started/introduction

[1] https://github.com/splitgraph/madatdata/tree/main/examples/r...

If you're interested, this is the "absolute minimum" React project I was able to create, using `esbuild` (see `dev.mjs`) and some .html files. [0] It's a sub-package in a larger workspace, so there is some complexity inherited from the monorepo in terms of tsconfig.json and dependency management, but you can ignore that; the esbuild part was pleasantly simple to implement, and it pretty much "just works," such that each file in `www` is an entrypoint with one corresponding script from `pages/` that calls `createRoot(container).render()`.

[0] https://github.com/splitgraph/madatdata/tree/main/packages/t...