# SQLite as a payload A SQLite database file is a compact, typed, self-describing payload — often a better wire format than JSON. Serve the `.sqlite` file directly and read it in the browser with QIP components that weigh 10–21 KB, instead of shipping the 849 KB official engine for read-only work. The same bytes stay compatible with the official `sqlite3.wasm`, so an app can render instantly with a tiny reader and lazily upgrade to the full engine only when someone needs SQL or writes. The [comparison below](#same-result-much-less-to-load) proves both readers return the identical result. ## Browse a database This lists every table with its columns and declared types. The database arrives like any other asset: a `` element pointing at [/data/countries.sqlite](/data/countries.sqlite) (48 KB).
```html
``` The `` element is the input and the wasm `` is the pipeline. The input's `type` attribute must match the component's declared `application/vnd.sqlite3` input type. ## Any table to CSV The [Titanic dataset](/data/titanic.sqlite) (68 KB) holds eight tables. Pick one and `sqlite-table-csv.wasm` (19 KB) converts it to CSV, entirely in your browser.

Uniforms come from ordinary form controls: the `

## Bring your own database Drop any SQLite file here and browse its schema. Nothing is uploaded: the file is read locally into the component's memory. Until you choose a file, the preview falls back to the countries database.

Databases should be published with `VACUUM INTO 'payload.sqlite'` — that guarantees a single clean UTF-8 file with no WAL sidecar and no freelist bloat. The readers deliberately reject WAL-mode and UTF-16 files with a clear error rather than risk stale or garbled reads. ## Same result, much less to load Both readers below convert the Titanic `Observation` table (891 rows) to CSV: the 19 KB QIP component, and the official 849 KB `sqlite3.wasm` running `SELECT *`. The outputs are compared byte for byte.

The official engine remains the right tool for SQL queries, joins, and writes. The point is sequencing: readers this small make it practical to treat `.sqlite` as a first-class response format, then load the full engine only for the minority of sessions that edit. ## CLI equivalent ```bash go install github.com/royalicing/qip@latest # List tables, columns, and types qip run modules/application/vnd.sqlite3/sqlite-schema.wasm -i mydb.sqlite # Convert the second table to CSV qip run modules/application/vnd.sqlite3/sqlite-table-csv.wasm '?table=1' -i mydb.sqlite > table.csv # Fetch one row by rowid qip run modules/application/vnd.sqlite3/sqlite-row-lookup.wasm '?table=0&rowid=42' -i mydb.sqlite # Count rows qip run modules/application/vnd.sqlite3/sqlite-table-count.wasm -i mydb.sqlite ``` These modules expect `application/vnd.sqlite3` input. The CSV converter outputs `text/csv`, so it composes with any downstream CSV component.