Database-Specific

Using WhoDB with PostgreSQL

This page covers what is specific to PostgreSQL when you use it through WhoDB: connecting, how the sidebar and grid present your data, and which WhoDB features apply.

Connecting

Select Postgres on the login page. The form asks for:

Hostname (required) — you can also paste a full postgres:// connection URL and WhoDB parses it into the fields.
Username and Password (required).
Database (required).
Search Path (optional) — restrict browsing to specific schemas.

Advanced options include Port (defaults to 5432) and an SSL mode selector ranging from disabled to full certificate verification (PostgreSQL's disable, require, verify CA, and verify-full).

Tip

For production databases, connect with a read-only role. WhoDB edits rows directly from the grid, so browsing with a read-only user prevents accidental changes.

How WhoDB Presents PostgreSQL

The sidebar shows a schema dropdown; browsing is scoped to the selected schema. System schemas such as information_schema, pg_catalog, and sys are hidden automatically.
Tables and views appear as storage units. Tables support row viewing, inserts, updates, deletes, and data import; views are read-only and expose their definition.
Column types, primary keys, and foreign keys are read from the catalog, so the grid and graph reflect your actual schema.

WhoDB Features with PostgreSQL

Scratchpad — run PostgreSQL SQL, including multiple statements in one cell. See Scratchpad.
Graph view — visualizes foreign-key relationships between tables in the selected schema. See Graph View.
Where conditions — the filter builder offers PostgreSQL operators, including ILIKE/NOT ILIKE for case-insensitive matching alongside LIKE, BETWEEN, IN, and IS NULL. See Where Conditions.
Mock data generation — generates rows for tables and follows foreign-key dependencies so parent rows are created first. See Mock Data.
Export — CSV and Excel from the grid or Scratchpad results. See Export Options.

Tips

Add a LIMIT to exploratory Scratchpad queries on large tables; unbounded SELECT statements pull every row.
Use Search Path at login to keep the schema dropdown focused when a database has many schemas.
Filter with the where-condition builder before exporting so the file contains only the rows you need.

Compatible Databases

CockroachDB, YugabyteDB, and QuestDB speak the PostgreSQL wire protocol and appear as their own entries on the login page, with the same PostgreSQL-style experience (QuestDB is table-scoped and has no schema dropdown).