DataGrip 2023.1

Working with code

• DataGrip can now add a space between the EXISTS keyword and the left parenthesis which can be toggled with a new setting. If you want to preserve the old Formatter behavior (without the space), you can change the Space after keyword setting to No in Preferences | Editor | Code Style | SQL (Queries tab).
• BigQuery: The WINDOW clause is now supported.
• ClickHouse: Сase settings when completing exact-case names are now ignored.
• MySQL: FOR UPDATE in nested queries is now supported.
• MySQL: The ENCRYPTION syntax is now supported.
• ClickHouse: EPHEMERAL columns, INTERSECT, and EXCEPT clauses are now supported.

Database explorer

• Data source content statistics are now again displayed in the Quick Documentation popup.

Introspection

• Oracle: Implemented several improvements to speed up introspection on Level 1, especially when the fast internal catalog is used.
• You can now check whether you have already been granted the SELECT_CATALOG_ROLE and the SELECT ANY DICTIONARY permission. This gives you access to the Oracle internal catalog and makes introspection much faster, because Oracle conventional catalogs are quite slow.
• Oracle: Cross schema database triggers are now supported. You can create a trigger X in schema A to table E in schema B, and it will be shown in schema B under the host table E.
• MySQL: The ROW_FORMAT clause/syntax is now supported.
• MySQL: The DDL of a table is now refreshed after changing a comment in the Modify dialog.

Connectivity

• Microsoft SQL Server: Current schema detection now works for any database.
• SQLite: The SQLite native library is now unpacked to the system folder.

Object editor

• Added a source editor to the Modify view.
• PostgreSQL: Virtual view creation is now also available in read-only mode.

Data editor/viewer

• Added an Alternate row colors setting for results tables. When the checkbox is enabled, rows will have alternating colors.
• PostgreSQL: It is now possible to update a value in a view with the ENUM column.
• Oracle: JSON columns are now supported.
• MongoDB: Added the Change Default action to configure the default page size.

SQL Resolve

• A setting to specify the default resolve mode used in the console has been added to Preferences | Database | Query execution | Other.
• Oracle: Type attributes are now supported.
• Oracle: Shortcut navigation now works for packages.

Navigation and search

• Oracle: When navigating to a routine, you are now taken by default to its implementation instead of its header.

SQL Generation

• Microsoft SQL Server, PostgreSQL and DB2: You can now use the Specify next value for sequences option to control the behavior of sequences that have a start value.
  • If the Specify next value for sequences option is not enabled, DataGrip generates the DDL of the sequence, adding the start value to the START WITH start_value.
  • When the Specify next value for sequences option is enabled, DataGrip adds the next value that the sequence should have to the DDL, with a few differences for the following databases:
    • Microsoft SQL Server: Instead of the sequence start value, the next sequence value is specified in the RESTART WITH clause in the CREATE and ALTER statements.
    • PostgreSQL: Instead of the sequence start value, the next sequence value is specified in the START WITH clause in the CREATE statement. The start value is specified in the START WITH clause, and the next value is in the RESTART WITH clause in the ALTER statement.
    • DB2: Instead of the sequence start value, the next sequence value is specified in the START WITH clause in the CREATE statement. The next value is specified in the RESTART WITH clause in the ALTER statement (changing the start value is not allowed in DB2).