DataGrip 2023.1.x

Released: Mar 28, 2023

Aggiornamenti in 2023.1.x

2023.1.2

Updated May 17, 2023

Features

  • Snowflake
    • The LIKE ALL operator is now supported.
    • New aggregate functions are now supported.
    • The functions MIN_BY and MAX_BY are now supported.
    • Added support for string literals as a body for Snowflake Scripting procedures.

Fixes

  • A memory leak that occurred when exporting data to a file has been fixed.
  • Add/Clone/Delete Column menu items no longer disappear when editing a CSV file in table mode.
  • Several bugs in the SQL formatter have been fixed.
  • The source text is now generated correctly in the Create view dialog.
  • Node disabling for SQL resolution scopes now works correctly.
  • [PostgreSQL] PostgreSQL 16 detection has been fixed.
  • [SQLite] Partial index generation has been fixed.
  • [Azure] The default browser now opens as expected when connecting.
  • [Redshift] External schemas are now clearly distinguished on the Schemas tab in data source properties.
  • [MySQL] Explain plan submenus are displayed correctly for MySQL Aurora.
  • [MySQL] Duplicated collations have been removed from DDL types.
  • [Snowflake] Highlighting for Python user-defined functions has been fixed.

2023.1.1

Updated Apr 17, 2023

Fixes

  • The delay in showing database object tooltips is back.
  • External schemas are now shown correctly in the Database Explorer.
  • Fixed an issue with the unresponsive Сancel button in the Modify dialog.
  • Autocompletion in the data editor filter field functions properly.
  • The Save LOB action works correctly for in-editor results.
  • SingleStoreDB is now recognized correctly.
  • [PostgreSQL] Fixed the permission issue that was causing synchronization to stop.
  • [MySQL] Unsupported SSL protocol errors are detected properly, and quick-fix suggestions are now shown.
  • [MySQL] The ALTER COLUMN syntax that changes the column default value has been fixed.
  • [MySQL] Creating users from the console now triggers automatic introspection. Users are shown in the database tree.
  • [Microsoft SQL Server] Fixed an introspection issue that previously occurred when connecting to Microsoft SQL Server 2005/2008.
  • [Microsoft SQL Server] The Add Row action is now enabled for tables with generated columns.
  • [SQLite] Automatic data source creation when opening SQLite files works correctly.
  • [Snowflake] Schemas with over 10,000 columns now load successfully.

2023.1

Updated Mar 28, 2023

Features

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).

Fixes

Working with Code

  • Fixed the problem where SQL Formatter didn't apply the right style for a subquery in the EXISTS clause. Now it works as expected.
  • Fixed the bug with saving style settings. If you have configured a special style for SQL2016 and the Inherit general SQL style checkbox in Preferences is not enabled, then you will need to reconfigure it.
  • MySQL: Problems with LAG and LEAD functions have been fixed.
  • Microsoft SQL Server: Inspections no longer erroneously report extra code.
  • PostgreSQL: The issue with Place constraints has been fixed.
  • PostgreSQL: DDL navigation to security policies now works as expected.
  • PostgreSQL: The SQL generator now quotes EXCLUDE constraints correctly.
  • BigQuery: Alias resolution in UNNEST queries now works correctly.
  • MongoDB: The bug with broken SQL completion for nested properties has been fixed.

Database explorer

  • Renamed folders in the database explorer no longer disappear.
  • PostgreSQL: The Drop context menu command now works as expected.

Introspection

  • Microsoft SQL Server: Quick Definition now works as expected.
  • PostgreSQL: When using the REFERENCING clause, the trigger's DDL is generated correctly.
  • DB2: Fixed an issue with interrupting object introspection. If the user permissions did not allow retrieving a list of database users, the rest of the database objects were not loaded either. Now everything except the list of users will be loaded.
  • Redshift: Fixed a performance issue. Introspection time is now significantly decreased.

Connectivity

  • Microsoft SQL Server: The issue with connecting via pg_bouncer has been fixed.

Data editor/viewer

  • There are no more empty spaces in in-editor results, as the table now adjusts its height to match the height of the results.
  • The correct font color is used in the data editor header.
  • PostgreSQL: The Quick Doc window doesn't freeze anymore when counting rows.
  • Support request: Image preview works correctly in the value editor.
  • BigQuery: The precision for milliseconds in the TIMESTAMP values is no longer lost.

Query console

  • Named parameters are detected correctly.
  • Whenever you copy and paste something, the IDE now correctly analyzes the selection (instead of the cursor position).
  • The schema switcher works properly in the new UI.
  • Oracle: Semicolons are no longer omitted in Oracle Aggregate Functions.
  • BigQuery: The Unexpected value error no longer pops up when previewing a table.
  • Failing queries with the Read access is allowed from inside read-action (or EDT) only notification in the Query console has been fixed.
  • Oracle: The CREATE PROCEDURE and CREATE FUNCTION now end with ";" - as expected.
  • MongoDB: Loss of values in IN (...) if there are more than 10 has been fixed.

SQL Resolve

  • Oracle: Fixed a few problems with Oracle collection methods:
  • Public synonyms are now correctly placed in the PUBLIC schema.
  • Recursive references to nested routines are resolved correctly.
  • Cursor parameter references qualified by a cursor name are resolved correctly.
  • Incorrect usages of %TYPE are reported as warnings.
  • Oracle: Fixed the resolution of standard attributes for collection types (for example, COUNT).
  • Oracle: Named arguments in type constructor calls are resolved correctly.

Diagrams

  • Fixed a bug where the IDE would show the Explain Plan diagram only for the first of several queries.
  • Errors no longer appear while saving a diagram.

SQL Generation

  • The Schema diff viewer now works properly, previously it opened empty if there were database or server objects included.