Database

If the cursor is inside a statement, perform the following actions:

• Ask what to execute: display a popup where you can select what part of a statement or statements to execute.

  

• Smallest statement: execute the smallest statement from the script. For example, when the cursor is inside a subquery, the subquery is executed.

• Largest statement: execute the largest statement from the script. For example, when the cursor is inside a subquery, an outer statement is executed.

• Largest statement or batch: execute the largest statement or a batch of statements from the script. For Transact-SQL (SQL Server and Sybase), the current batch of statements is executed. For all other dialects, the same as the previous option.

• Whole script: execute the whole script.

• Everything from caret: execute everything below the caret.

If the cursor is outside of a statement (for example, on a blank line or within a comment), perform one of the following actions:

• Nothing: stop execution.

• Whole script: execute the whole script.

• Everything below caret: execute everything below the caret.

If the code is selected (highlighted), perform one of the following options:

• Exactly as one statement: execute exactly what is selected as a single statement.

• Exactly as statements: execute exactly what is selected. If the selection contains more than one statement, the statements are executed as separate statements.

• Smart expand to script: expand a selection to form a sequence of valid statements. For example, if there is at least one statement border within the selection, the selection is expanded to form a sequence of valid statements. This sequence is then executed. Otherwise, execute what is selected.

You can select to view query results on individual tabs, or on one and the same tab. For the single tab, the tab is updated for each query.

Select the checkbox to create a new tab with query results each time you run the SELECT query. Using this approach, you can keep results of all the queries that you have run.

If the checkbox is cleared, the same tab is used to show query results. Information on the tab is updated to show the result.

In this case, when you get the result that you want to keep, you can pin the tab to the tool window () on the toolbar or Pin Tab in the context menu for the tab).

Set the query parsing for unsupported databases that use SQL:2016 or Generic dialects. The Generic dialect differs from SQL:2016 in error highlighting. In the Generic dialect, all found errors are not highlighted.

• On valid ANSI SQL statements or by separator: CLion analyzes a script and splits it on valid statements or by separators. This setting is default.

• On ANSI SQL statements: split scripts according to the SQL:2016 grammar.

• By statement separator: extract and run statements by separators. For the Generic dialect, the separator is a semicolon.

Display results of the query that you run under the query in the editor, not in the results pane of the Services tool window.

The following screenshot shows the results when the checkbox is selected.

When the checkbox is cleared, the results are in the Services tool window.

Create a new tab for a data source sessions and output results.

Select the checkbox to display errors in output and input panes. Clear this checkbox to display information about errors in the output pane only.

The error notification bar might be useful when you run sequences of SQL statements. If an error occurs, you see a notification bar with possible actions to fix the error.

When you run a statement with parameters, CLion saves parameter values in memory. Select this checkbox and next time you execute the statement, CLion will show you the last used parameter values. You can change them before running the statement.

Clear this checkbox and CLion will execute the statement immediately without showing you the parameter values.

Select to display the console toolbar in the editor.

When you create, delete, or rename a schema, CLion updates the list of available schemas in the introspection scope window. To see the introspection scope, click the button near the data source name in the Database tool window.

Select to display warnings for potentially unsafe queries.

If you forgot to put the WHERE clause in DELETE and UPDATE statements, CLion displays a notification to remind you about that. If you omitted the WHERE clause intentionally, you can execute current statements as you planned.

You can define a tab title in the comment section before the query. In the Treat text as title after field, you can reserve a combination of symbols or characters, and any text after this combination will be treated as a tab title. By default, no combination is used, so any text after -- or /* is treated as a tab title.

To disable this feature, open settings Ctrl+Alt+S, navigate to %database_general%, and clear the Create title for results from comment before query checkbox.

Open settings by pressing Ctrl+Alt+S, navigate to %database_general%.

In the Treat text as title after field, define a combination for tab titles.

Adds a schema name to the table name for the tab. If the checkbox is selected, double-click the table in the Database tool window to see a qualified tab name.

On	Off

Show a confirmation dialog when you close Add Database, Add Schema, Create New Table, or Modify Table dialogs. Close means clicking Cancel or pressing Escape. If the checkbox is cleared, the dialog closes instantly.

Skip the Object Migration dialog if changes in the object's source code are valid.

By default, the Object Migration dialog is displayed to confirm changes that you make to source code in objects. For example, if you modify code in a routine or a view and press Submit, you will see the Object Migration dialog with your changes highlighted.