sqlite-loader-wit

Canonical WIT contract for SQLite WebAssembly extensions. Defines the interface a .wasm extension implements so it can be loaded into a SQLite host — whether that host is native SQLite + a WASM runtime (sqlite-wasm-loader) or SQLite-compiled-to-WASM (sqlite-wasm).

Vendored into both consumers as a git submodule.

Package

sqlite:extension@0.1.0

Files

File	Contents
types.wit	Shared types: sql-value (variant), error, enums, records
host-spi.wit	Host-imported SPIs: spi, prepared, transaction, schema, logging, config, state, cache, random, text, hashing, encoding
guest.wit	Guest-exported interfaces: metadata, lifecycle, scalar-function, aggregate-function, collation, authorizer, update-hook, commit-hook
world.wit	Six capability-graded worlds: minimal, stateful, lifecycle-aware, authorizing, hooked, full

Design

Declarative registration. Extensions don't imperatively call register-scalar-function(...) on the host. They export a single metadata.describe() that returns a manifest listing every scalar function, aggregate, and collation they provide, with guest-assigned IDs. The host calls describe() once after instantiation and wires everything up. The host then dispatches by calling back into the corresponding interface (scalar-function.call(func-id, args), aggregate-function.step(func-id, context-id, args), etc.).

Variant sql-value. SQL values use the idiomatic component-model variant:

variant sql-value {
    null,
    integer(s64),
    real(f64),
    text(string),
    blob(list<u8>),
}

Capability-graded worlds. Pick the smallest world that fits the extension. A pure scalar function uses minimal. A stateful aggregate uses stateful. Mix in lifecycle, authorizer, or hooks as needed. Use full only when you genuinely need the kitchen sink.

Versioning

Pre-1.0. Breaking changes bump the 0.x minor.

License

MIT