SQL

Confirm the active tab’s connection before executing. Dockwave sends SQL with that database user’s permissions; the read-only result grid does not restrict what SQL can change.

Run a read-only example

SELECT current_database() AS database_name,
       current_user AS user_name;

Use Run or Command+Enter. A non-empty selection executes that selected text; without a selection, Dockwave executes the entire buffer, not just the statement under the cursor. Plain Enter inserts a newline. Check the selection before every run, especially when the buffer contains several statements.

For example, with no selection this buffer produces two result boundaries:

SELECT 1 AS first_result;
SELECT 2 AS second_result;

Use the result navigation to move between outputs. Results are loaded progressively within a bounded window: a loaded row count is not necessarily the total number of rows on the server. A truncated result is not a complete dataset. Fetch-more paging is available for supported cursor workflows, not a promise that every arbitrary SQL buffer can be paged.

Stop is a request, not a rollback

Stop requests server-side cancellation and waits for PostgreSQL to acknowledge it. If it remains unacknowledged, the interface reports that state after a bounded wait; it does not guarantee the server has stopped.

The quick switcher offers disconnect if you need to abandon the session. Neither a Stop click nor an uncertain connection failure proves what already ran, and cancellation is not a rollback of previously committed effects. Inspect transaction and server state before retrying SQL that can change data.

Editor assistance has limits

Syntax highlighting and schema-aware completion help write SQL; PostgreSQL remains the authority on validity. Column completion supports resolved alias. contexts. Do not assume bare, unprefixed column completion is available in every position.

History and saved queries belong to their connection profile. Restored SQL is a local document, not a restored live database session.

Next step

Read the export warning before exporting: export runs SQL again rather than saving the visible grid.