Skip to content

Interactive browser preview

The preview below uses the same SQLBraid SQLite WASM adapter that an application bundle can use. Write or paste a SQL statement, then run it against an official SQLite WASM :memory: database in a Web Worker. The fixture is deterministic finance data with Korean and other Unicode account names.

Try:

  • SELECT statements, including your own filters and joins;
  • INSERT, UPDATE, and other single-statement commands against the disposable database;
  • readable SQLite syntax/runtime errors, followed by a corrected query;
  • Inspect schema to see the seeded table definition; and
  • Reset seeded database to restore the original rows after a mutation.

The result table shows at most the first 1,000 rows so exploratory queries stay responsive. A worker that runs longer than ten seconds is replaced and its database is reset.

The SQL is intentionally user-authored raw text inside this disposable database: the preview does not interpolate it into a server query, claim injection safety, or persist any changes.

Live SQLBraid playground

Change a Braid query and run the rendered SQL

The controls below change a real SQLBraid tagged template. Braid conditionals are rendered in a Web Worker, values stay bound, and the resulting statement executes against a disposable SQLite WASM database.

Braid · worker · :memory:

Change the query

Clear a filter to make its @braid if branch disappear. Projection and sort changes use structural fragments rather than value binds.

Braid source

Loading example…

Ready. Change the controls and run the Braid query.

Rendered SQL

Run a query to see the statement sent to SQLite.

Bound parameters

[]

Variant: not rendered

Query results

Seeded database schema
finance_accounts (
  account_id INTEGER PRIMARY KEY,
  account_name TEXT NOT NULL,
  balance INTEGER NOT NULL,
  currency TEXT NOT NULL,
  locale TEXT NOT NULL
)

Raw SQL scratchpad

Want to prove the database itself is live? Edit this SQL directly. This path intentionally uses sql.raw() only inside the disposable browser database.

The default path deliberately does not require OPFS, persistence, SharedArrayBuffer, or COOP/COEP headers. A production application can choose another SQLite WASM storage mode separately; this documentation preview stays portable on static hosting such as GitHub Pages.