Export

Export re-executes the editor’s SQL. It is not a snapshot of the visible grid. It uses the current selection, or the entire buffer if nothing is selected. It does not export only the selected grid rows or the grid’s filtered view.

Export a read-only result

Connect the tab and put one read-only query in the editor, or select exactly that query:
```
SELECT 1 AS example_id, 'Dockwave' AS example_name;
```
Wait until the session is idle. Export and interactive execution share the session and cannot run there simultaneously.
Choose Export CSV or Export JSON in the results toolbar. The JSON option produces JSON Lines, not a JSON array.
Choose a destination in the save dialog. Export streams to a file without relying on the grid’s retained row window.
Wait for Export complete. The success notification offers a Finder reveal; check the resulting file before relying on it.

Formats and limits

CSV includes a header and CSV escaping for fields that require it.
JSON Lines writes one JSON object per row. Non-null PostgreSQL values, including numbers and booleans, are represented as JSON strings; SQL NULL becomes JSON null.
Export expects one result set. Multiple result sets or a command-only buffer are errors, not a supported multi-output export.
The grid’s row limit does not define the export size. Large exports can take time and consume disk space.

Cancellation and failures

Use Stop to request cancellation. The same acknowledgement limitations described in the SQL guide apply. Cancellation cannot undo SQL effects that already happened.

A failed or cancelled export is not a completed file. The export path writes through a temporary file and only publishes a successful result; do not interpret a missing final file as proof that the SQL never ran.

Return to the guide.