Serve
The other half of connecting: publishing a catalog for those clients to attach. Three ways, in increasing order of how much of your own code is involved — a schema file with no code at all, a permission layer over it, and an in-process bridge with no server or network anywhere.
- Host a SQL filen6kd takes a schema.sql and serves it as a network catalog. No application code, one stateless container.
- PermissionsA YAML file grants read or readwrite per table, verified at boot — and the same tables can be served as two catalogs with different rules.
- In-processThe same per-table permission model between two DuckDB connections in one process — no network, no server, no protocol.