@plurnk/plurnk-execs-sqlite

SQLite runtime executor for plurnk-service's exec scheme. Runs the sqlite runtime tag in-process via Node's builtin node:sqlite — no subprocess.

A @plurnk/plurnk-execs-* sibling built on the plurnk-execs framework.

Runtime tag

| Tag | Glyph | Engine | | -------- | ----- | ------------------------------------------- | | sqlite | 🗃 | node:sqlite in the supported Node runtime |

Database target

The EXEC target slot is the database file; with no target it defaults to an ephemeral in-memory db:

## EXEC0 [sqlite]
SELECT * FROM users;

## EXEC0 [sqlite] (./app.db)
SELECT * FROM users;

With no target, a fresh :memory: database exists for that operation only. State does not persist across EXECs. Pass a file path for persistence.

Transient tabular calculations

With no target, :memory: is a scratch calculator over ad-hoc tables — build one inline with VALUES and aggregate, no schema or file needed:

## EXEC0 [sqlite]
WITH t(item,qty,price) AS (VALUES ('a',3,2),('b',1,5)) SELECT sum(qty*price) AS total, sum(qty*price)*1.0/sum(qty) AS avg_price FROM t;

Use floats to avoid integer truncation. SQLite integer division truncates — 11/4 → 2. Multiply by 1.0 (or CAST(x AS REAL)) to force real division: 11*1.0/4 → 2.75. Any division over integer columns needs this, or the result is silently floored.

Output

Writes to the results channel as application/json, ready for the jsonpath body-matcher (plurnk-mimetypes' JSON handler):

• Row-returning statements (SELECT, RETURNING, PRAGMA) → an array of row objects.
• Mutations (INSERT/UPDATE/DELETE/DDL) → { changes, lastInsertRowid }.

The query/mutation split is decided by the prepared statement's columns(), never by parsing the SQL. One statement per EXEC. Errors return RFC 9457 Problems in the terminal operation result.

Configuration

The framework's PLURNK_EXECS_ERROR_DETAIL_LIMIT bounds SQLite diagnostics and rejected SQL tails included in Problem facts.

Availability & proposal gating

probe() reports available because node:sqlite is part of the supported Node

=26 runtime. effect(target) marks :memory: and no target as pure, while a file-backed database is host. The former bypasses the proposal gate and the latter requires it; both produce their result through the background stream path ({§executor-effect}). Classification uses only the target, never the SQL.

Tests

test:lint, test:unit.