JOIN completion
It knows your schema. Even the join.
Tables behind FROM, the columns of an alias behind o., and behind JOIN the whole condition, taken from the foreign key.
An error is underlined at the place the database names, with its code, detail and hint beside it.
Ctrl+Space Cmd/Ctrl+Enter
WHERE tables as tables
Filter, sort, follow the key.
Open a table and filter it with conditions; the values are always bound, never written into the SQL. Sorting happens on the server.
F4 on customer_id = 3 shows that customer, Alt+F7 lists every table that points to the row, with counts.
F4 Shift+F4 Alt+F7
UPDATE edit data
Change cells. Nothing is sent while you type.
Changes are collected and shown in colour: changed, new, to delete. Look at them as SQL, undo them, then write them together in one transaction: all rows or none.
A row somebody else changed in the meantime is reported, not overwritten.
F2 Cmd/Ctrl+S Cmd/Ctrl+D
EXPLAIN execution plan
See where the time goes.
The plan of every database as one tree table: rows estimated and actual, own and total time. The expensive operation and the wrong estimate stand out, with a hint in words.
“With execution” runs the statement inside a transaction that is rolled back.
Cmd/Ctrl+K Cmd/Ctrl+X
REFERENCES ER diagram
The schema as a picture.
A whole schema, or one table with its neighbours. It arranges itself, tables can be moved, and the same content is there as lists.
Export as SVG, Mermaid or DBML.
DELETE protection
Production says so. And asks.
A connection gets a level: free, ask before writing, or read only. Every statement is classified in the backend, the window only puts the question.
Transactions show their state as the server reports it; closing a tab with an open one asks first.
Every feature in detail