Fast, safety-first PostgreSQL/MySQL CLI for developers — schema-aware autocomplete, natural-language shortcuts, and previews before anything destructive runs.

MidQL is a modern alternative to psql/mysql built around two ideas:

• Speed — raw SQL is first-class with schema-aware tab completion, and a rule-based natural-language layer turns show users where rank 20 into SQL faster than you can type the full SELECT. Cross-table filters like select users which has money > 20 discover the JOIN path from foreign keys automatically.
• Control — DELETE/UPDATE/DROP show the affected rows and ask for confirmation before running, production connections are visually distinct and can be locked read-only, and every statement is written to a local audit history.

Everything runs offline: the natural-language engine is rule-based and schema-driven. No API keys, no telemetry.

npm install -g midql-cli

Requires Node 18+. The installed command is midql.

midql postgres://user:pass@localhost:5432/mydb

midql (mydb:mydb)> show users where rank > 10
→ SELECT * FROM "users" WHERE "rank" > $1   $1=10
┌────┬───────┬───────────────────┬──────┐
│ id │ name  │ email             │ rank │
...

midql (mydb:mydb)> SELECT count(*) FROM orders JOIN users ON users.id = orders.user_id;

Plain English and raw SQL work side by side — input that starts with a SQL keyword and looks like SQL runs as-is; everything else goes through the natural-language engine. The generated SQL is always previewed under the input line before you press Enter, and echoed with the results after.

Operator words: is, is not, greater than / more than / over / above, less than / under / below, at least, at most, contains, starts with, ends with, between … and …, in a, b or c, is null, is not null. Combine with and/or (and binds tighter).

Table and column names are matched fuzzily against the live schema — singular/plural (user → users), underscores (firstname → first_name), and small typos (usres → users) all resolve. When a reference is genuinely ambiguous, MidQL lists the candidates instead of guessing; qualify with table.column to be explicit.

All values are sent as bound parameters — never interpolated into SQL — so injection through the natural-language layer is structurally impossible.

• destructive (DELETE/UPDATE with WHERE): MidQL first runs a count and a 10-row sample of the affected rows, shows them, and asks Proceed? [y/N] (default No).
• catastrophic (DROP TABLE, TRUNCATE, DELETE/UPDATE without WHERE): confirmation requires typing the table name. Statements without a WHERE clause are called out explicitly.
• \safe off reduces checks to a one-line warning — except on connections tagged prod, where safety is always enforced and the prompt turns red (midql (prod:mydb)!>).
• \readonly on (or readonly: true in the profile) blocks every write before it reaches the driver.
• One-shot mode (midql query) refuses destructive statements without --yes and prints the row count it would have affected.
• Every input is appended to ~/.midql/history.jsonl with timestamp, connection, generated SQL, and outcome — a local audit trail.

• Input starting with a SQL keyword runs as raw SQL on a pinned session connection, so BEGIN / COMMIT / ROLLBACK work naturally; an open transaction shows a [tx] badge in the prompt.
• Tab accepts the top completion (verbs → tables → columns → operators, context-aware in both NL and SQL modes). Columns reachable through a foreign key are annotated (accounts, joined).
• ↑/↓ history, Ctrl+R history search, Ctrl+C clear line (twice to exit), Ctrl+A/E home/end, Esc dismiss.

midql profiles add main --dialect postgres --host db.example.com --database app \
  --user deploy --password-env PGPASSWORD --env prod --readonly

midql profiles list
midql main                                  # open the REPL on a saved profile

midql query "count users" --db main
midql query "delete users which has rank 0" --db dev --yes
midql query "show users" --db main --format json > users.json

midql backup --db main                      # pg_dump -Fc → midql-app-<timestamp>.dump
midql restore backup.dump --db dev --yes

Environment tags (--env dev|staging|prod) color the prompt and harden confirmations on prod. Backup/restore shells out to pg_dump/pg_restore/psql/mysqldump/mysql; if a tool is missing MidQL tells you how to install it or set an explicit path in the config.

~/.midql/config.json:

{
  "profiles": [],
  "safety": "on",
  "maxJoinDepth": 3,
  "tools": { "pgDumpPath": null, "pgRestorePath": null, "psqlPath": null, "mysqldumpPath": null, "mysqlPath": null }
}

Set MIDQL_HOME to relocate the config directory.

Saved passwords are encrypted with AES-256-GCM using a random key generated at first run into ~/.midql/.key (file mode 600). This protects against casual disclosure of the config file — it is not a defense against an attacker with full access to your OS account. Prefer --password-env to reference an environment variable, or omit the password entirely for URL-based ad-hoc connections.

npm install
npm test                                     # unit tests (no database needed)
docker compose -f docker/docker-compose.yml up -d --wait
npm run test:int                             # integration tests against seeded PG 16 + MySQL 8
npm run build

The natural-language engine is pure functions over a schema snapshot — see test/fixtures/ for the schemas the unit tests run against.

MIT © Eser Sariyar