Docs
Console

SQL editor

Run SQL in the browser against a real Postgres engine with the Console's PGLite-powered editor.

The Console includes an in-browser SQL editor for running queries, inspecting results, and exploring a schema without leaving the browser. It's powered by PGLite — the same real PostgreSQL engine compiled to WebAssembly that Silos runs on the server — so the SQL semantics you see in the editor match the engine your database uses.

Opening the editor

Open a database

From the dashboard, select the database you want to query.

Open the SQL editor

Switch to the SQL editor tab. You get a query pane and a results grid.

Run a query

Type SQL and run it. Results appear below, with column types and row counts.

What you can run

Because the editor runs a genuine Postgres engine, you can use the full SQL surface — DDL and DML, transactions, PL/pgSQL, views, CTEs, window functions, and JSON/JSONB. For the complete picture of what's supported, see PostgreSQL compatibility.

CREATE TABLE notes (
  id     bigserial PRIMARY KEY,
  body   text NOT NULL,
  tags   jsonb DEFAULT '[]'::jsonb,
  added  timestamptz DEFAULT now()
);

INSERT INTO notes (body, tags)
VALUES ('first note', '["intro"]');

SELECT id, body, tags FROM notes ORDER BY added DESC;

The in-browser editor is a real Postgres engine running locally in your browser tab via PGLite. It's ideal for quick exploration, prototyping a schema, and learning — and the same schema and SQL carry over to a deployed Silos database with no engine swap. See Browser & PGLite.

When to use the editor vs. a client

  • Use the SQL editor for quick checks, ad-hoc queries, prototyping a schema, and exploring data visually.
  • Use a Postgres client or driver (psql, pg, psycopg) for application work, scripts, and anything you want to version-control. See Connecting → Drivers.

Next steps

On this page