Naming
A result is named after the table it came from. When there is no single table, the statement names itself, and a line comment written above the statement wins over the SQL:monthly totals. Names longer than 28 characters are truncated with an ellipsis, and a result no statement stands behind falls back to Result 1. Rest the pointer on a tab to see the query that produced it, or the error message if it failed.
Working with the strip
A pinned result moves to the front of the strip, and the next query opens a new tab instead of overwriting it. Pinned tabs cannot be closed or cleared until you unpin them, which is what makes them useful for comparing two runs side by side.
Picking a result moves the editor cursor to the statement that produced it and unfolds that statement if it was collapsed. Picking the result already showing does nothing, so clicking between pinned results never moves the editor under you. A statement you have since edited away leaves the cursor where it is.
The results panel expands itself when a query runs. The toolbar’s trash button clears the query and the results together; to keep the query, right-click the results and choose Clear Results.
The row cap
ASELECT or WITH query with no LIMIT, FETCH FIRST or TOP of its own stops at the row cap.
Your SQL reaches the server exactly as you wrote it. The cap applies to the rows read back, so a
query carrying its own LIMIT, FETCH FIRST or TOP is never touched, and EXPLAIN, SHOW,
writes and DDL are never capped. Both numbers are in Settings > Data
(Data settings).
When the cap trims a result the status bar reads Showing N rows and offers Fetch All, which extends the result in place. To skip the cap for one run, press Cmd+Option+Enter or choose Execute Without Limit from the Execute button’s menu.