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 on an official SQLite WASM :memory: database in a Web Worker. The fixture is deterministic finance data. Some account names are Korean or use other Unicode characters.

Try these things:

  • SELECT statements, with your own filters and joins;
  • INSERT, UPDATE and other single-statement commands on the disposable database;
  • a SQLite syntax or runtime error, then a corrected query;
  • Inspect schema, to see the table definition of the seed data;
  • Reset seeded database, to restore the original rows after a change.

The result table shows only the first 1,000 rows. This keeps exploratory queries responsive. If a worker runs for more than ten seconds, the preview replaces it and resets its database.

The SQL is raw text that you write, inside this disposable database. This is intentional. The preview does not interpolate it into a server query. It does not claim injection safety. It does not keep 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 does not require OPFS, persistence, SharedArrayBuffer or COOP/COEP headers. This is intentional. A production application can select a different SQLite WASM storage mode separately. This documentation preview stays portable on static hosting such as GitHub Pages.