dblab CLI

Q: How do I enable read-only access?

Use --readonly and restrict database-role permissions as well.

Q: How do I open a saved profile?

Run dblab connect and select the named connection. The profile supplies its saved parameters for the new session.

dblab is a terminal SQL client with saved connection profiles and optional password storage in the operating system keyring.

3,247 ★ on the repository
Last commit Nov 4, 2026
MIT

CLI

danvergara/dblabAuthor:danvergara

Install

Manual install

brew install --cask danvergara/tools/dblab

First Installation-section method.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

The client executes SQL with the database role’s rights and retains local query history.

This is third-party code. Review the repository files before installing.

What it does

dblab is a SQL client that opens databases in a three-pane terminal UI: table navigation, SQL editing and results with metadata. It supports PostgreSQL, MySQL and SQLite. Users can also connect to Oracle and SQL Server. The editor uses Vim modes and can execute the current query only. Saved profiles keep connection parameters, with passwords in the OS keyring. The `--readonly` flag opens a read-only connection to prevent accidental writes.

Who it is for. Analysts working across SQL systems who want one terminal interface for tables, schemas and queries.

Good fit when

An unfamiliar database needs tree and metadata inspection.
SQL is easier to edit beside results in a modal editor.
Several environments need named connection profiles.
Exploration requires an explicitly read-only session.

Not a fit when

One session must manage multiple databases simultaneously.
Statement order matters but queries would be run as one parallel batch.
You need a non-interactive API rather than a terminal UI.

Example request

Prepare a dblab profile for the test database with encryption and read-only mode. Show settings without the password.

Limitations

Each session connects to one database; confirm its connection and database name before querying. Up to five editor statements may run concurrently, so execute dependent queries separately. Local history retains SQL, including its literal values, which matters for confidential data. SSL is disabled by default in connection settings. Configure encryption before opening the first remote database connection.

How to disable. Finish or cancel the query and exit dblab. When removing a profile, separately remove unwanted keyring credentials and saved SQL from local history.

FAQ

How do I enable read-only access?

Use `--readonly` and restrict database-role permissions as well.

How do I open a saved profile?

Run `dblab connect` and select the named connection. The profile supplies its saved parameters for the new session.

How do I run the current query only?

Ctrl-R runs the cursor-line query by default; Ctrl-E runs the editor contents.

Is there table pagination?

No. Use SELECT with explicit LIMIT and OFFSET for large tables.

Where are indexes shown?

Select a table and open the Indexes result tab; other tabs show columns and constraints.

How do I switch schemas without restarting?

For PostgreSQL or Oracle, press Ctrl-S and select a schema. Switching is available when no schema was pinned at startup; the status bar shows the selected name.