Lataa DataGrip (EAP) 261.20869.40

Data Source and Drivers dialog improvements
We have made a few changes to the Data Sources and Drivers dialog.

1. The Data Sources, Clouds, Drivers, and DDL Mappings sections are now the main tabs in the dialog, located on the left-hand side.
2. If the Comment field is empty, it is hidden by default. To display it, click Add Comment next to the Name field.
3. For the Driver dropdown, if the selected driver has not been downloaded, DataGrip shows a corresponding comment. To download the driver, click Download near the dropdown.
4. The Connection type dropdown options are now tabs. If a data source has more than three connection types, they are displayed as a dropdown.
Also, the Create DDL Mapping action has been removed. You can create a DDL mapping on the DDL Mappings main tab.
Files are created with the SQL dialect and data source attached
When chatting with AI Assistant in the AI Chat tool window, you can create a file from a code snippet.

If there is any context about the SQL dialect, a data source, or a schema provided in the chat, you don’t have to attach any of those or set the dialect because DataGrip will do this automatically. The same goes for questions about a file that already has a data source attached: DataGrip will attach that data source to the newly created file.

DataGrip will store the created file in the current project directory.
[Oracle] Intention action for suppressing the resolve inspection for back label references
We have made the Suppress for back label references option easier to find and use. Previously, it was only available in the Settings dialog under Editor | Inspections | SQL.

Now, it can be toggled in intention actions. To enable or disable it, open the list of intention actions by clicking Alt+Enter (Windows/Linux) or Option+Enter (macOS), navigate to Enable option “Suppress for back label references”, and select or deselect the Suppress for back label references checkbox.

Execute Selection as Single Statement action in the context menu
We have added the Execute Selection as Single Statement action to the context menu of a code selection. Use this when you need to execute a certain chunk of code and DataGrip isn’t parsing it properly.

Query Files folder in the database explorer
You can access your query files in the database explorer. We have added a Query Files folder that appears under each data source node. To toggle this folder's visibility, click View Options on the tool window toolbar, and then select or deselect the Query Files option.

Explain Plan
We have made a few updates to the Explain Plan workflow to make it more discoverable, informative, and easy to use:
- The list of options in the Explain Plan dropdown on the code editor toolbar has been shortened. Now it only has Explain Plan and Explain Analyse on it.

- In the Services tool window, the Query Plan tab that displays the plan has been moved to the same level as the Output and Result tabs. It also has a new icon now.

- In the Query Plan tab, you can now view details of each plan row in a separate panel on the right-hand side of the tab.

- For the cells that contain a table name, quick documentation is available in a popup when you hover the cursor over it.

- The different views available for a query plan are displayed in separate inner tabs. These inner tabs can be seen at the bottom of the Query Plan tab. They are hidden by default and appear only when more than one tab is open. To open the Total Cost or Startup Cost tab, click Flame Graph on the left-hand toolbar and select the view you need.

- You can now copy the query plan in the database’s native format, for example, JSON or XML. To do this, click the Copy Original Query Plan button at the top of the left toolbar. This is supported for PostgreSQL, Amazon Redshift, MySQL, MariaDB, Oracle, Microsoft SQL Server, and Snowflake.

[Microsoft SQL Server] Support for JSON indexes
DataGrip now supports creating and modifying JSON indexes for Microsoft SQL Server. You can work with them in code generation and also use the indexes in the Create and Modify dialogs.

Show Geo Viewer button on the toolbar
For better discoverability, we have moved the Show Geo Viewer button to the data editor toolbar.

Minor improvements
- In the IDE Settings dialog, under Editor | Code Style | SQL | <code_style>, the Inherit General SQL style checkbox now contains a link to the General SQL style settings page.
- DBE-14375, DBE-24796: The MATCH_RECOGNIZE expression support has been implemented for Google BigQuery and improved for Snowflake and Oracle.
Bug fixes
- DBE-25198, DBE-25199: Exporting and copying the column list of a table to the clipboard now works as expected.
- DBE-25131: For a query results grid in the Services tool window, deleting a row by pressing Delete now works as expected.
- DBE-24721: [Microsoft SQL Server] Pagination of the old database versions works as expected.
- DBE-24149: [Azure] Pagination for Fabric now works as expected.
- DBE-23159: [PostgreSQL] The Column should be in group by clause inspection and GROUP BY completion now both work as expected.
- DBE-16826, DBE-21071: [Azure SQL Database] Introspection now works as intended for Fabric and Dynamics 365.
- DBE-19117: [Snowflake] Explain Plan now works as intended.
- DBE-24860: The data source name can now be displayed near a file name in code editor tab headers.
- DBE-25156: [MongoDB] For *.js files attached to a data source, file execution now works as expected.
- DBE-24992: [PostgreSQL] The formatter no longer attempts to quote operators.
- DBE-24886: The behavior of the border around a statement was fixed for files outside the current project.
- DBE-24722: Diagrams work as expected for unquoted names in the introspection scope.
- DBE-24481: [Google BigQuery] Pipe syntax in CTEs works as expected.
- DBE-23084: The Datetime/timestamp settings can no longer be saved with an invalid date or time format.
- DBE-23930: You can once again simply double-click on a record from the Query History dialog to paste it into the query console.
- DBE-25256: Unshelving files now works as expected.
- DBE-20558: [Oracle] Support has been added for the field resolution on variables of cursor types.
- DBE-24925: [Oracle] Support has been added for named parameter notations in the :NEW syntax.
A few code highlighting bugs have been fixed:
- DBE-19313: [Oracle] Nested INTO clause inspection has been fixed.
- DBE-23795: [Oracle] Support has been added for ON OVERFLOW clauses in LISTAGG.
- DBE-24518: [Google BigQuery] Support has been added for TRANSACTION statements.
- DBE-23603: [Clickhouse] Support has been added for RECURSIVE CTEs.
- DBE-24516: [H2] Support has been added for the STRING_AGG built-in function.
- DBE-16645: [Microsoft SQL Server] The SET CONTEXT_INFO arguments work as expected.
- DBE-20733: [Microsoft SQL Server] Support has been added for the IGNORE NULLS and RESPECT NULLS keywords for analytic functions as part of the OVER clause.
- DBE-22202: [Microsoft SQL Server] Support has been added for the IS [NOT] DISTINCT FROM operator.
- DBE-24597: [Google BigQuery] ReservedWordsTest has been improved, and the list of reserved words now works as expected.
- DBE-24510: [Google BigQuery] Support has been added for the quantified LIKE operator.
- DBE-23495: [MariaDB] Support has been added for FLUSH TABLE[S] ... WITH READ LOCK AND DISABLE CHECKPOINT.
- DBE-23795: [Oracle] Support has been added for the DISTINCT and ALL keywords in LISTAGG.
- DBE-25317: [BigQuery] Support has been added for the RANGE syntax and associated built-in functions.
- DBE-15889: [Snowflake] Support has been added for CREATE EXTERNAL TABLE and CREATE EXTERNAL TABLE ... USING TEMPLATE.