Query consoles

Edit as Table

In INSERT statements, opens the editor for working with the data in a table format.

Change Dialect (<CurrentDialect>)

Change the SQL dialect. Select a dialect from the list.

Explain Plan

• Explain Plan: show an execution plan (or explain plan) for the current statement. The result is shown in a mixed tree/table format on a dedicated Plan tab.

  To build a diagram of the execution plan, click the Show Diagram icon () on the left of the Plan tab, or press CtrlAltShift0U.

  To build a flame graph, click the Flame Graph button ().

• Explain Plan (Raw): show an execution plan (or explain plan) for the current statement. The result is shown in table format. Technically, EXPLAIN <CURRENT_STATEMENT> or similar statement is executed.

Execute

CtrlEnter

Execute the current statement or the sequence of selected statements.

Execute to File

Execute the current statement and save results in a text file. Select the output format and specify the file location and name.

Run 'console [data_source]'

CtrlShiftF10

Execute all the statements in the query console.

Execute

CtrlEnter

Execute selected SQL statement or statements.

If nothing is selected, the current statement is executed.

Browse Query History

CtrlAlt0E

Open a dialog that shows all the statements that you have run for the corresponding data source.

See also, Use the Query History dialog.

View Parameters

Open or close the Parameters dialog.

Open the Tools | Database | Query Execution section of the Settings dialog to view or edit the query execution settings.

For more information about these settings, refer to Query Execution.

Transaction Mode

and

Transaction Isolation

Select the isolation level for database transactions and the way the transactions are committed.

• Auto: the current transaction is committed automatically when you submit your local changes to the database server.

• Manual: the changes submitted to the database server are accumulated in a transaction that can either be committed or rolled back explicitly by means of the Submit and Commit () or Roll Back () buttons on the toolbar.

For more information about database transaction modes and isolation, refer to Submit changes to a database.

Commit

Commit the current transaction. This button is available only for the manual transaction mode. See also, transaction mode and isolation.

Roll back

Roll back changes. This button is available only for the manual transaction mode. See also, transaction modes and isolation.

Cancel Running Statements

CtrlF2

Terminate execution of the current statement or statements.

File Resolve Mode

Select the resolve mode to manage the context that database objects in your code are resolved to.

• Playground: default mode for query consoles. All the database objects are resolved to the same context.

• Script: default mode for local SQL files. The USE SQL statement (SET search_path TO for PostgreSQL) overrides the default context that the database objects are resolved to.

For more information about the resolve modes, refer to Resolve modes.

In the following video, the public schema is selected as default for the query console. The schema contains the actor table, whereas the information_schema schema does not contain it. When the resolve mode is Playground, the database object is resolved to default schema in both SELECT statements, because all the statements are considered unrelated.

Once the resolve mode is changed to Script, the second SELECT statement is considered related to the SET search_path TO information_schema one. The actor table is no longer resolved in that statement.

In-Editor Results

Toggle the display of query result within the code editor of query console.

For more information about the in-editor results, refer to In-Editor Results.

<schema>

Switch current schema

Select the default schema or database. For PostgreSQL, Amazon Redshift, and Greenplum use the <schema> list to form the schema search path.

For more information about schemas, refer to Schemas.

<session>

Switch attached session

Select the database connection session.

For more information about the database connection sessions, refer to Managing connection sessions