DataGrip Changelog

What's new in DataGrip 2024.1 Build 241.14494.251

Apr 4, 2024

AI Assistant: option to attach schemas
Working with data
Simplification of sessions
Working with code

New in DataGrip 2023.3 Build 233.10527.14 EAP (Oct 19, 2023)

New in DataGrip 2023.2.2 Build 232.10072.15 (Oct 6, 2023)

New in DataGrip 2023.3 Build 233.9102.70 EAP (Oct 5, 2023)

New in DataGrip 2023.2 Build 232.8660.111 (Jul 21, 2023)

New in DataGrip 2023.2 Build 232.8660.5 EAP 2 (Jul 6, 2023)

New in DataGrip 2023.2 Build 232.7295.8 EAP (Jun 7, 2023)

New in DataGrip 2023.1.2 Build 231.9011.35 (May 17, 2023)

New in DataGrip 2023.1 Build 231.8109.78 EAP 3 (Mar 18, 2023)

Introspection:
[Oracle]: We've implemented several improvements to speed up the introspection on Level 1. Here are a few tips to speed up your work, especially if you're working with a large number of schemas and many database objects:
Switch the introspection level to Level 1, where DataGrip introspects only the names and types of objects.
On introspection Level 1, you can click Refresh selected object to edit a specific object or view its sources.
Check if you have the SELECT_CATALOG_ROLE and the SELECT ANY DICTIONARY permissions, which grant you access to the Oracle internal catalog. This makes introspection much faster.
Code highlighting:
DBE-11727, DBE-11500 [BigQuery]: Alias resolution in UNNEST queries now works correctly.
DBE-17291, DBE-17449 [ClickHouse]: EPHEMERAL columns, INTERSECT, and EXCEPT clauses are now supported.
Schema Diff:
[Microsoft SQL Server, PostgreSQL, 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).
Query console:
DBE-17479 Failing queries with the Read access is allowed from inside read-action (or EDT) only notification in the Query console has been fixed with regression.
DBE-12787, DBE-12109 [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.
Code completion:
DBE-13506 [MongoDB]: The bug with broken SQL completion for nested properties has been fixed.
Code completion:
We fixed the image preview in the data grid.
DBE-13329 [MongoDB]: We added the Change Default action to configure the default page size.

New in DataGrip 2023.1 Build 231.6890.13 EAP (Feb 10, 2023)

Working with code:
DBE-4469: We fixed the problem where SQL Formatter didn’t apply the right style for a subquery in the EXISTS clause.
DBE-14440 [H2]: We 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.
The other fixes in this area are more or less self-explanatory:
DBE-15973 [BigQuery]: The WINDOW clause is now supported.
DBE-9219 [Clickhouse]: Сase settings when completing exact-case names are now ignored.
DBE-14796 [MySQL]: Problems with LAG and LEAD functions have been fixed.
DBE-16311 [MySQL]: FOR UPDATE in nested queries is now supported.
DBE-12139 [MySQL]: The ENCRYPTION syntax is now supported.
DBE-13186 [Microsoft SQL Server]: Inspections no longer erroneously report extra code.
DBE-11946 [PostgreSQL]: An issue with Place constraints was fixed.
DBE-6276 [PostgreSQL]: DDL navigation to security policies now works as expected.
Database explorer:
DBE-17263: Data source content statistics is again displayed in the Quick Documentation popup.
DBE-10812 [PostgreSQL]: The Drop context menu command now works as expected.
Introspection:
DBE-12578 [Oracle]: Cross 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.
DBE-6986 [MySQL]: The ROW_FORMAT clause/syntax is now supported.
DBE-10603 [Microsoft SQL Server]: The Quick Definition now works as expected.
DBE-9087 [PostgreSQL]: When using the clause REFERENCING, the trigger’s DDL is generated correctly.
DBE-12404 [IBM Db2]: We 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 but the list of users will be loaded.
Connectivity:
DBE-16417 [Microsoft SQL Server]: Current schema detection now works for any database.
DBE-11012 [SQLite]: The SQLite native library is now unpacked to the system folder.
Object editor:
DBE-16393: We’ve added a source editor to the Modify view.
DBE-17329 [PostgreSQL]: Virtual view creation is now also available in read-only mode.
Data editor/viewer:
DBE-3572: We’ve added an Alternate row colors setting for results tables. When the checkbox is enabled, rows will have alternating colors.
DBE-16250: There are no more empty spaces in in-editor results, as the table now adjusts its height to match the height of the results.
Query console:
DBE-14074: Named parameters are detected correctly.
DBE-10555: Whenever you copy and paste something, the IDE now correctly analyzes the selection (instead of the cursor position).
DBE-12109 [Oracle]: Semicolons are no longer omitted in Oracle Aggregate Functions.
DBE-16871 [BigQuery]: The Unexpected value error no longer pops up when previewing a table.
SQL Resolve:
DBE-16831: A setting to specify the default resolve mode used in the console has been added to Preferences | Database | Query execution | Other.
DBE-5497 [Oracle]: We 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.
DBE-12772 [Oracle]: We fixed the resolution of standard attributes for collection types (for example, COUNT).
Explain plan:
DBE-17137: We fixed a bug where the IDE would show the Explain Plan diagram only for the first of several queries.
Navigation and search:
DBE-12015 [Oracle]: Go to Declaration (Ctrl/Cmd+B or Ctrl/Cmd+click) now navigates you to the routine implementation.

New in DataGrip 2022.3.3 Build 223.8617.3 (Jan 12, 2023)

New in DataGrip 2022.3.2 Build 223.8214.62 (Dec 22, 2022)

New in DataGrip 2022.3.1 Build 223.8214.6 (Dec 9, 2022)

New in DataGrip 2022.3 Build 223.7571.180 (Dec 2, 2022)

New in DataGrip 2022.3 Build 223.7571.73 EAP 3 (Nov 19, 2022)

New in DataGrip 2022.3 Build 223.7255.83 EAP 2 (Nov 2, 2022)

New in DataGrip 2022.3 Build 223.6646.21 EAP (Oct 13, 2022)

New in DataGrip 2022.2.5 Build 222.4345.5 (Sep 29, 2022)

New in DataGrip 2022.2.4 Build 222.4167.25 (Sep 12, 2022)

New in DataGrip 2022.2.3 Build 222.4167.22 (Sep 8, 2022)

New in DataGrip 2022.2.2 Build 222.3739.67 (Aug 23, 2022)

This bug-fix update is focused on enhancing the new Modify Object UI. Before listing what we’ve improved, let us give you a bit more background info about how the new UI came about.
Why the new UI?:
At some point it became clear that the whole Modify Object UI had to be rewritten from scratch. There were some usability issues, like expanding the UI, which we admit was not the best idea. However, the main reason was that with so many supported database engines, DataGrip just could not provide a powerful UI for objects in each of them. We could manually design the dialog for 3 or maybe 5 databases, but not for 25 of them.
In each database engine, objects have lots of specific attributes, and we would like our users to have the UI to see and edit those attributes. The only good approach here was to generate the UI on a metadata basis, so that whatever the object has inside would find its way to the UI. DataGrip didn’t explicitly know what controls the Modify dialog would be populated with, though. That is why we rewrote the dialog from scratch.
Issues with the new UI
The first version of the new UI, marked simply New UI, was released in March 2022, so our users had the opportunity to try it for the last 4 months and to share their feedback. The new UI became the default option in the 2022.2 EAP. Most of the feedback, though, came after the official release.
Not only was the dialog re-written, but lots of new functionality was added, as well. It is now possible to edit constraints and to set the collation for the table, and there’s now a basis for multiple object editing.
However, some of the scenarios became more difficult to manage, and others went missing completely. The most critical issues had to do with creating primary and foreign keys. We appreciate your feedback on these issues, which has helped us fix them in this 2022.2.2 release.
Improvements in DataGrip 2022.2.2:
You can pin an editing pane and make it into a tab.
You can explore the object tree without opening the corresponding editing pane. In other words, you can choose whether a single-click or a double-click will let you edit the object.
The kebab menu next to the column name lets you create a primary key or a unique constraint. The action creates a new tab in the background.
Foreign keys and indexes can be created from the context menu of the column, pre-filling the column information:
Completion now works for the names of columns in indexes and primary and foreign keys:
The names of indexes and keys can be auto-generated. If you don’t like this behavior, you can turn it off by clicking on the ‘two circular arrows’ button next to the object’s name.
Buttons are now available for invoking code completion, which makes it not only more discoverable but also accessible for die-hard mouse fans. The down arrow invokes code completion to substitute a value, that is, to choose another type. The right arrow invokes code completion to add something to a value, such as an UNSIGNED attribute in MySQL.
The ‘New’ action now respects the context: If you invoke it from the ‘columns’ node, a column will be created. Or if you invoke it from the table name in the left-hand pane, a popup will appear to let you choose an object:
New and edited objects are highlighted in green and blue, respectively. Modified fields are in blue.
The changes to an object or field can be reverted:
Escape doesn’t close the window silently. Instead it will now warn you that you’re about to lose your changes.
There is one known issue: If you have previously selected ‘Don’t ask again’ in this dialog, unfortunately there is no way to bring this option back. We’re going to fix that in the next update.
If you run into any errors while executing a generated script, the dialog will not close after the execution attempt:

New in DataGrip 2022.2.1 Build 222.3345.126 (Jul 28, 2022)

New in DataGrip 2022.2 Build 222.3345.35 EAP 4 (Jul 12, 2022)

New in DataGrip 2022.2 Build 222.3244.4 EAP 3 (Jun 30, 2022)

New in DataGrip 2022.2 Build 222.3048.12 EAP 2 (Jun 21, 2022)

Playground and Script resolve modes:
Resolving database objects in SQL scripts takes an understanding of what the objects mean. This is necessary for the IDE to provide you with correct code completion and treat the usages of the objects as links.
In general, the resolve context should match the running context, but that is not a trivial task for DataGrip to handle. This is why there were, until recently, several resolve-related problems. Here’s what would sometimes happen:
All the objects were resolved, but the script could not be run in the database.
When the Auto-qualify option was turned on, the objects would sometimes stay unqualified if they were located in the default database/schema.
If there were multiple objects with the same name in different databases/schemas, existing columns would fail to be resolved (or vice versa, there was a risk of resolving non-existing columns), and even the Expand column list action would sometimes generate the wrong list.
The cause of these and other issues was that, for each console or local file, DataGrip resolved their objects to the context (selected in the top right-hand drop-down) and the default database/schema (or the entry from the SQL Resolution scopes setting, if one was provided).
This was fine for working with scripts containing USE/SET SEARCH PATH statements, which switch the context. However, the IDE needs to know where to resolve right from the beginning of the file, too. So, it treated the default database/schema (or the entry from the SQL Resolution scopes setting, if one was provided) as the most appropriate context for the beginning of the file.
In other words, if there are no USE/SET SEARCH PATH statements in your file, then DataGrip shouldn’t try to resolve the beginning of the file somewhere out of context. To address this situation, we’re created a way for DataGrip to know which approach to follow, by introducing two resolve modes: Playground and Script.
In Playground mode, DataGrip resolves objects according to the context (which is the value in the schema chooser, the resolution scope, or, if none of those is set, the default database). It works best if your file is just a set of unconnected queries, independent of each other and having no particular sequence – kind of like a playground. Playground mode is now the default for query consoles.
In Script mode, the beginning of the file is resolved to the context (which is the value in the schema chooser, the resolution scope, or, if none of those is set, the default database), but any USE statements in the script change the context for the resolve because they are part of the script’s sequential logic. It is a good choice for when your queries have sequential logic and should be run as a single script. Script mode is now the default for local files.
Switching between the modes is easy – just use the drop-down on the toolbar.

New in DataGrip 2022.1.5 Build 221.5787.39 (Jun 9, 2022)

New in DataGrip 2022.2 Build 222.2889.12 EAP (Jun 3, 2022)

Option to import multiple CSV files:
You can now select several CSV files and import them at once!
New Modify UI:
The new Modify UI, a basic version of which was introduced in the 2022.1 release, has become the default option. Starting with version 2022.2, all of a table’s child objects can be added and edited using this new UI.
Give this feature a try and share your feedback with us!
The old UI will remain available through this release cycle via the context menu.
Categories in keymap:
Previously, all of the actions related to database functionality were stored in four different places in the keymap:
Database | Database Explorer
Database | Query Result
Plugins | DataGrip customization
Plugins | Databases Tools and SQL
This structure, which admittedly has very little logic, was a historical consequence of the IDE’s development.
To help you see all the available actions, we’ve re-arranged the structure and placed all of the actions in groups under the Database parent group.
Scopes in DDL data sources:
You can now set file scopes as sources for DDL data sources. This will let you combine several folders into one DDL data source easily.
[Oracle, Vertica] Password expiration warning:
Oracle and Vertica databases can provide warnings if the password is going to expire. DataGrip now retrieves this information and displays it after Test Connection is activated.
[SQL Server] Support for collations and charsets:
Collations and charsets are now generated with the table’s DDL.
Basic DB support:
We’ve added 3 new databases to the basic support list: DuckDB, Mimer SQL, Apache Ignite.
Quality improvements:
Data editor:
DBE-10971: The table order is now saved in the data editor.
DBE-7888: February is back in the date picker!
DBE-15454: Binary columns with mixed content types are now editable.
DBE-7804: CSV import no longer fails on the last line if the last value is empty and there is no new line.
DBE-15335: The SQL-Insert-Multirow extractor generates the correct query.
Query Console:
DBE-996: The search bar no longer hides the toolbar.
DBE-11616: [ClickHouse] MODIFY ORDER BY is supported for ALTER TABLE.
DBE-14643: [SQL Server] The condition is always false warning no longer appears during variable assignment.
DBE-12232: [SQL Server] CHANGETABLE is now supported.
DBE-13312: [SQL Server] END CONVERSATION is now supported.
DBE-12435: [SQLite] The PRAGMA_TABLE_INFO and PRAGMA_TABLE_XINFO tables are resolved.
DBE-14997: [PostgreSQL] Columns are now correctly resolved when using CTE with INSERT INTO.

New in DataGrip 2022.1.4 Build 221.5591.57 (May 12, 2022)

New in DataGrip 2022.1.3 Build 221.5591.46 (May 9, 2022)

New in DataGrip 2022.1.2 Build 221.5591.9 (Apr 27, 2022)

New in DataGrip 2022.1.1 Build 221.5080.224 (Apr 15, 2022)

New in DataGrip 2022.1 Build 221.5080.155 (Apr 8, 2022)

New in DataGrip 2022.1 Build 221.5080.106 EAP 4 (Apr 2, 2022)

New in DataGrip 2022.1 Build 221.5080.35 EAP 3 (Mar 23, 2022)

New version of Modify Table:
We are slightly reworking the Modify Table window. The new version will have a fully generated UI based on introspective properties, which will allow it to have a variety of database-specific parameters.
For now we are releasing only a small portion of the update, but it can already be uniquely useful. The new Modify Table window lets you add and edit column check constraints, which was previously impossible! Also, you can now edit all the properties of tables and columns DataGrip knows about.
We think you will particularly appreciate the new UI for columns because there is no collapsing or expanding, which many users found annoying.
Reworked settings:
The structure of the preferences settings for the Database section hasn’t changed since the first version of DataGrip. We decided it was time to improve the section’s usability by updating the structure. Here’s what we’ve come up with:
The Track databases/schemas creation and deletion setting has been moved from the General section. This setting identifies whether the introspection needs to run after you create or delete schemas in the query console.
There will be one tiny inconvenience. These settings will be reset to default values:
Data Source properties | Track databases/schemas creation and deletion – True.
Database | Database Editor and Viewer | Sort tables by numeric primary key – False.
Database | Other | Show database refactoring preview – True.
Editor | General | Editor Tabs | Database | Always show qualified names for database objects in tab titles – False.
Editor | General | Editor Tabs | Database | Shorten datasource and object names in tab titles – True.
Data editor:
We’ve fixed some problems related to the date picker:
DBE-8561: Clicking outside the date picker no longer loses the changes.
DBE-9632: The Enter key works for saving the value in the date picker.
DBE-11706: The Tab key is now supported in the date picker.
Code editor:
We’ve also addressed a number of issues regarding code highlighting:
DBE-11683: [PostgreSQL]: Added support for ROWS FROM syntax.
DBE-11868: [PostgreSQL]: Fixed a problem resulting in unresolved common table expressions.
DBE-11830: [Oracle] Added support for USING INDEX ENABLE syntax.
DBE-6548: [Oracle] Fixed column resolve in CREATE MATERIALIZED VIEW LOG statements.
DBE-15095: [Snowflake] Added support for the WITH TAG option in the CREATE STAGE statement.
DBE-14793: [Snowflake]: Added support for the EXECUTE statement.
Database diff viewer:
DBE-15063: The new smart algorithm for string comparison solved the problem where keyword casing was respected in the diff window.

New in DataGrip 2022.1 Build 221.4906.1 EAP 2 (Mar 1, 2022)

New in DataGrip 2022.1 Build 221.4165.70 EAP 1 (Feb 11, 2022)

Import/Export:
New:
Copy multiple objects.
Quality improvements:
DBE-5200: Edit as table action works correctly even when the rows in the source file have different numbers of columns.
DBE-14541: Adding a row to a one-column CSV file works correctly.
DBE-14735: Fixed the bug with simultaneous export of tables containing timestamps.
Data editor:
New:
Default display format for binary cells.
[MongoDB] Editing fields in results.
Quality improvements:
DBE-13040: Better usability for displaying hidden columns – simply click on a hidden column in the column list.
DBE-14516: Better usability for the cell size indicator – it isn't shown for fully loaded values and has a monospaced font, so the content is aligned neatly.
DBE-10851: Fixed a UI glitch in the data tree view.
The context menu of the column is also displayed in the Transpose view.
Introspection:
New:
YugabyteDB added to basic support.
DBE-13521: [ClickHouse] the source code of the materialized views is now introspected.
Code generation:
New:
DBE-5136: [SQL Server] You will now get a valid script when removing columns with constraints via Modify Table.
Quality improvements:
DBE-14760: [MySQL] The Modify Table window no longer corrupts the function index.
DBE-14801: [Snowflake] The generated DDL script contains the statements for creating the default sequences.
Database diff viewer:
Quality improvements:
DBE-14686: The Reformat generated code option is respected.
DBE-14782: Diff viewer detects objects that are likely to be the same even if their names are different.
DBE-14431: [Oracle] The Array index out of bounds exception should no longer occur.
Code editor:
New:
Convert to subquery intention.
Better auto-indent algorithm.
Quality improvements:
DBE-11247: [Snowflake] JSON is correctly highlighted inside statements.
DBE-14504: [ClickHouse] Map literals are supported.
Known issue:
The Services tool window fails to appear in some cases, often when the project being used is more than several months old. Performing a settings restore often helps.

New in DataGrip 2021.3.4 Build 213.6777.22 (Jan 19, 2022)

New in DataGrip 2021.3.3 Build 213.6461.82 (Dec 29, 2021)

New in DataGrip 2021.3.2 Build 213.6461.19 (Dec 16, 2021)

New in DataGrip 2021.3.1 Build 213.5744.178 (Nov 27, 2021)

New in DataGrip 2021.3 Build 213.5744.174 (Nov 23, 2021)

Data editor:
Aggregates:
We’ve added the ability to display an Aggregate view for a range of cells. This is a long-awaited feature that will help you manage your data and spare you from having to write additional queries! This makes the data editor more powerful and easier to use, bringing it a step closer to Excel and Google Spreadsheets.
Select the cell range you want to see the view for, then right click and select Show Aggregate View.
Keeping your database in the VCS:
Mapping the DDL data source and the real one:
This release is a logical continuation of the previous one, which introduced the ability to generate a DDL data source based on a real one. Now, this workflow is fully supported. You can:
Generate a DDL data source from a real one: see the 2021.2 announcement.
Use the DDL data source to map the real one.
Compare and synchronize them in both directions.
Just as a reminder, a DDL data source is a virtual data source whose schema is based on a set of SQL scripts. Storing these files in the Version Control System is a way to keep your database under the VCS.
There is a new tab in the data configuration properties, DDL mappings, where you can define which real data source is mapped to each DDL data source.
Connectivity:
Accidental spaces warning:
If any value except User or Password has leading or trailing spaces, DataGrip will warn you about them when you click Test Connection.
LocalDB as a dedicated data source SQL Server:
SQL Server LocalDB has its own dedicated driver in the driver list. This means that it has a separate type of data source which should be used for LocalDB. Here’s how it helps:
The LocalDB connection is more explorable.
You only need to set the path for the executable once, in the driver options, and it will be applied for all data sources.
Kerberos authentication Oracle, SQL Server:
It’s now possible to use Kerberos authentication in Oracle and SQL Server. You need to obtain an initial ticket-granting ticket for the principal by using the kinit command, which DataGrip will use when you choose the Kerberos option.
Enable DBMS_OUTPUT Oracle, IBM Db2:
This new option in the Options tab lets you enable DBMS_OUTPUT by default for new sessions.
More options button:
We’ve added a More Options button for when you need to configure something unusual for a connection. The currently available options include the ability to add Schema and Role fields for Snowflake connections, and two menu items for configuring SSH and SSL to increase their discoverability.
Expert options:
The Advanced tab now includes a list of Expert Options. In addition to the option to turn on the JDBC introspector (please contact our support before using this!), the following database-specific options are available:
Oracle: Disable incremental introspection, Fetch LONG values, and Introspect server objects
SQL Server: Disable incremental introspection
PostgreSQL (and similar): Disable incremental introspection and Do not use xmin in queries to pgdatabase
SQLite: Register REGEXP function
MYSQL: Use SHOW/CREATE for source code
ClickHouse: Automatically assign sessionid
Introspection:
Introspection levels Oracle:
Oracle users have been experiencing a problem with DataGrip’s introspection, which took a long time if they had lots of databases and schemas. Introspection is the process of getting the metadata of the database, such as object names and source code. DataGrip needs it to provide rapid coding assistance, navigation, and search.
Oracle system catalogs are rather slow, and the introspection was even slower if the user had no admin rights. We did our best to optimize the queries to get the metadata, but everything has its limitations.
We realized that for most daily work, and even for effective coding assistance, there is no need to load object sources. In many cases, just having database object names should be sufficient to provide proper code completion and navigation. So, we introduced three levels of introspection for Oracle databases:
Level 1: Names of all supported objects and their signatures, excluding names of index columns and private package variables
Level 2: Everything except source code
Level 3: Everything
Introspection is fastest on level 1 and slowest on level 3.
Query Console:
Check for boolean expressions:
One of our users tweeted about an unfortunate situation: he executed the UPDATE query on a production database with the condition WHERE id - 3727 (instead of =) and had millions of records updated!
We were also surprised that MySQL allows that, but such is life. But we wouldn’t be the DataGrip team if we didn’t add an inspection for that! Please welcome the check for boolean expressions in WHERE and HAVING clauses.
Extract function for queries:
Now queries can be extracted as a table function. To do this, select the query, invoke the Refactor menu, and use Extract Routine.
JOIN cardinality inlay hint:
The new inlay hint will tell you the cardinality of a JOIN clause. There are three possible options: one-to-one, one-to-many, and many-to-many. If you want to turn it off, you can adjust the setting in Preferences | Editor | Inlay Hints | Join cardinality.
Code completion for database names MongoDB:
Database names are completed when using getSiblingDB, and collection names are completed when using getCollection.
Additionally, field names are completed and resolved if used from a collection that was defined with getCollection.
Services tool window:
Timestamps in output hidden by default:
In line with this request, timestamps are no longer shown for query output by default. If you want to return to the previous behavior, you can adjust the setting in Database | General | Show timestamp for query output.
New activation settings:
If you use the Services tool window in window mode, by default it is hidden behind the IDE. With the new setting you can pass the focus to it every time you run a query, so it will appear after the query has finished.
Also, if you are annoyed when finishing a long query in some other console activates the corresponding tab in the Services tool window, select the Activate Services output pane for selected query console only checkbox.
Import/Export:
New UI for importing data:
When importing .csv files or copying tables/result sets, you will observe the following improvements:
You can choose an existing table or create a new one.
You can change the target schema in the import dialog. The dedicated dialog for the target will not appear if you copy a table or result set.
The target is saved as default per schema. So, if you are constantly copying from one particular schema to the other, there will be no need to choose the target each time.
Miscellaneous:
New Bookmarks tool window:
Before we had two very similar instances – Favorites and Bookmarks. As the difference between the two could sometimes be confusing, we’ve decided to stick to just one – Bookmarks. We’ve reworked the workflow for this functionality and made a new tool window for it.
From now on, all the objects or files you mark as important (with the F3 shortcut on macOS or F11 on Windows/Linux) will be located in the new Bookmarks tool window.

New in DataGrip 2021.3 Build 213.5744.9 EAP 3 (Nov 11, 2021)

New in DataGrip 2021.3 Build 213.5449.24 EAP 2 (Oct 28, 2021)

New in DataGrip 2021.3 Build 213.4631.26 EAP (Oct 12, 2021)

New in DataGrip 2021.2.4 Build 212.5457.41 (Oct 8, 2021)

New in DataGrip 2021.3 Build 213.4631.26 EAP (Oct 7, 2021)

Data editor:
Aggregates:
We’ve added the ability to display an Aggregate view for a range of cells. This is a long-awaited feature that will help you manage your data and that will spare you from having to write additional queries! This brings our data editor step closer to Excel and Google Spreadsheets!
Independent split:
If you split the editor and open the same table, the data editors will now be completely independent. You can set different filtering and ordering options for them. Previously, filtering and ordering were synchronized, which obviously was useless.
Custom font:
You can choose the dedicated font for looking at data under Database | Data views | Use a custom font.
Setting for default sorting:
You can define which sorting method will be used as the default for tables: via ORDER BY or client-side (which doesn’t run any new queries and sorts only the current page). The setting can be found under Database | Data views | Sorting | Sort via ORDER BY.
Display mode for binary data:
16-byte data is now displayed as UUID by default. You can also customize how binary data is displayed in the column.
Database in the Version Control System:
TLDR:
This release is a logical continuation of the previous one, which introduced the ability to generate a DDL data source based on a real one. Now, this workflow is fully supported. You can:
Generate a DDL data source from a real one
Use the DDL data source to map the real one
Compare and synchronize them in both directions
Just as a reminder, a DDL data source is a virtual data source whose schema is based on a bunch of sql scripts. Storing these files in the Version Control System is a way to keep your database under the VCS.
Database in the VCS: step-by-step workflow:
Let’s take a look at the whole process. Imagine two developers, Alice and Bob, want their data source schemas to be synchronized via GitHub.
We advise users to store the project root folder in the VCS. Alice and Bob will sync their projects, which contain the DDL data sources for the sakila database. They both have their local data sources, but they want to synchronize them via VCS.
Alice enables version control integration on a project root folder, which is usually automatically displayed in the Files tool window.
She then creates a sakila_repo folder, which she’ll use as a schema representation to be synced via VCS.
First, Alice needs to create the DDL data source with help of the Dump to DDL data source action. This will be a file-based schema mirror of the real data source. It’s name is Sakila Alice DDL.
When creating a DDL data source, it’s necessary to specify that the files will be placed in the sakila_repo folder.
DataGrip asks whether Alice wants to add new files to Git, and indeed she does.
Now the project, along with the sakila_repo folder, can be committed and pushed to the GitHub repo. Alice hasn’t defined the remote repo yet. This can either be done in advance or when the project is pushed.
Auto-sync:
If this option is turned on, the DDL data source will be automatically refreshed with changes to the corresponding files. This was already the default behavior, but now you have the option to disable it.
Initial search path:
In this UI you can define names for your database and schemas, which will be displayed in the DDL data source. DDL scripts don’t usually contain names, and in these cases there will be dummy names for databases and schemas by default.
Connectivity:
Accidental spaces warning:
If any value except User or Password has leading or trailing spaces, DataGrip will warn you about them when you click Test Connection.
[Oracle, SQL Server] Kerberos authentication:
It’s now possible to use Kerberos authentication in Oracle and SQL Server.
[Oracle, DB2] Enable DBMS_OUTPUT:
This new option in the Options tab lets you enable DBMS_OUTPUT by default for new sessions.
More options button:
We’ve introduced a More Options button for cases when something unusual has to be configured for the connection but there’s no need to clutter up the UI. These options currently include the ability to add Schema and Role fields for Snowflake connections and buttons for configuring SSH and SSL to increase their discoverability.
Expert options:
The Advanced tab now includes an Expert Options list. In addition to a common option to turn on the JDBC introspector (please contact our support before using it), there are some database-specific options:
Oracle: Disable incremental introspection, Fetch LONG values, Introspect server objects.
SQL Server: Disable incremental introspection.
PostgreSQL (and similar) : Disable incremental introspection, Do not use xmin in queries to pgdatabase.
SQLite: Register REGEXP function.
MYSQL: Use SHOW/CREATE for source code.
Clickhouse: Automatically assign session id:
Database explorer:
Table view for tree nodes:
Pressing F4 on any schema node allows you to see the table view of the node’s contents. For example, you can get a view of all tables:
Or a table’s columns:
All data viewer capabilities are available here: you can hide/show columns, export to many formats, and use text search.
[Clickhouse] Distributed tables:
Distributed tables are now placed under a dedicated node in the database explorer
Query Console:
Timestamps in output hidden by default:
In line with this request, timestamps are no longer shown for query output by default. If you want to return to the previous behavior, you can adjust the setting in Database | General | Show timestamp for query output.
[MongoDB] Code completion for database names:
Database names are completed when using getSiblingDB, and collection names are completed when using getCollection.
Additionally, field names are completed and resolved if used from a collection that was defined through code completion.
Import/Export:
‘First row is header’ auto-detection:
Starting from this version, when you open or import a CSV file, DataGrip automatically detects that the first row is the header and contains the names of the columns.

New in DataGrip 2021.2.3 Build 212.5457.16 (Sep 30, 2021)

New in DataGrip 2021.2.2 Build 212.5284.17 (Sep 3, 2021)

New in DataGrip 2021.2 Build 212.4746.86 (Jul 28, 2021)

New in DataGrip 2021.2 Build 212.4746.16 EAP 3 (Jul 15, 2021)

New in DataGrip 2021.2 Build 212.4416.10 EAP 2 (Jun 24, 2021)

New in DataGrip 2021.1.3 Build 211.7442.53 (Jun 8, 2021)

New in DataGrip 2021.2 Build 212.3724.3 EAP (Jun 4, 2021)

DDL data source:
Generation from a real data source:
It is now possible to generate a DDL data source based on a real one. The DDL files will be created on the disk and the new data source will be based on them. That way you’ll always be able to regenerate these files and refresh the DDL data source.
Let’s take a look at how it works:
The new menu item Dump to DDL data source is added to the SQL Scripts context menu.
In the open dialog, you need to specify the folder where the newly created files will be stored.
In the Generation tab, specify the options on how these DDL files should be generated.
After clicking OK the DDL data source is created.
And the folder with the new files is automatically attached to your project.
DDL data source generation is another step in our long-term development of seamless database versioning. With this feature, you can keep your DDL files under a VCS system and regenerate them every time your database structure is updated.
Creating objects:
Starting in this version, you can create objects in a DDL data source via the UI. The corresponding files will be created on the disk.
Diagrams
Two important features have been added to diagrams:
Table comments are now visible
Colors of tables are also displayed on the diagram
Introspection
[PostgreSQL] Virtual foreign keys for pg_catalog:
Some time ago, we announced the mechanism for creating virtual foreign keys. Now we’ve used this mechanism and covered pg_catalog with virtual foreign keys. This brings a couple of improvements.
First, the JOIN completion helps you when querying system tables:
Second, navigation by data in system tables works:
[Oracle] Tablespaces:
We added support for tablespaces, data files, and temporary files. They are now introspected:
And included in DDL generation:
SQL editor:
Search in Local History:
Now if you are looking for a particular revision in the local history, you can use text search for help!
[SQL Server] Completion for cross-database synonyms:
Code completion for cross-database synonyms is now available.
INSERT completion and computed columns:
Computed columns are taken into account when completing INSERT statements – they are not included in the suggested item.
Long tab names are back:
After receiving some feedback from users who didn’t like the shortened tab names, we introduced the option to change them back. If you prefer long tab names, you can simply uncheck the Shorten Tab Titles option.
Maximize Editor / Normalize Splits action:
For a long time we had the Hide All Tool Windows action, which could be called by double clicking on a tab or with the Shift+CtrlCmd+F12 hotkey. Many users treated it as a Maximize Editor action and it worked as such!
After we introduced the split mechanism, the situation became more complicated: should this action hide the split tabs or not? So we did the following:
Hide All Tool Windows action doesn’t hide the split tabs.
The new action Maximize Editor / Normalize Splits maximizes the current tab, but doesn’t hide the tool windows.
Working with data:
Context live templates from the data editor:
Introduced in the previous release, context live templates now work from the data editor. If you’re working with a table and you wish to query it, you can easily do so with the help of the SQL scripts action!
Qualification in navigation by foreign keys:
If you have foreign keys pointing to the objects in another schema and these objects have the same names, they will be displayed as qualified in the foreign keys navigation UI:
Option for additive sorting:
The recently introduced Alt+Click for additive sorting (instead of just Click) wasn’t convenient for some users. If you are one of them, you can now change the value here:
Table link after import:
When you finish an import, a link to the new table appears in the notifications.
Other
Managing the popping up of Services tool window:
When a query returns no data, there’s no need for the Services tool window to appear if it was hidden already. Now you can define which operations make the Services tool window appear on your own.
Back and forward buttons in Settings:
These buttons make it easier to navigate in the Settings window and not get lost there.
Signatures in navigation:
Now when you are searching for a function, procedure, or operator, we show the signature in the Go To window. This helps when you use overloading heavily!
Quality improvements
General:
DBE-12079: [PostgreSQL] We’ve reworked the introspector. The main effect of the new introspector for the end-user is no more object duplicates!
DBE-13164: No more freezing when typing JOIN statements along with using virtual foreign keys.
Import/Export:
DBE-13259: Export of numeric fields doesn’t fail if there are non-numeric values.
DBE-11370, DBE-13139, DBE-12536: Import became faster for PostgreSQL, Redshift, Exasol, Hive, Clickhouse, DB2, and HSQL.
DBE-11370: Import became faster with the help of multi-insert statements for Hive, Clickhouse, DB2 and HSQL.
Data editor:
DBE-12545: ORDER BY field size is saved.
DBE-13055: Time zone is always shown for values with the timezone.
DBE-9814: [Oracle] DATE type values don’t display time if no time is set.
DBE-12679: [Oracle] Filtering by DATE field is possible.
DBE-12716: [DB2] Filtering by binary, blob, char for bit data, and varchar for bit data fields is possible.

New in DataGrip 2021.1.2 Build 211.7442.38 (Jun 1, 2021)

Features:
DBE-13048: Some run configurations require the data source to be disconnected first. Now it’s possible to disconnect from a data source before launch.
DBE-12906: We’ve introduced a Modify grants action.
Introspection:
DBE-6276: [PostgreSQL] Support for security policies.
DBE-13138 [Redshift] Support for sort keys for tables and views.
DBE-13024: [Redshift] Fixed the bug with the completely failed introspection.
DBE-12442: [Oracle] Source code is retrieved correctly for Oracle 9i.
DBE-13146: [Oracle] Type attributes are retrieved correctly for Oracle 11.
DBE-12954: [BigQuery] No more missing schemas.
DBE-12166: [BigQuery] Creating a temporary function doesn’t re-run the introspection.
Navigation and search:
DBE-12901: It’s possible to navigate to the data source from the Database tab of the search.
DBE-11738: The Context data source scope works again in search.
DBE-12968: Color settings are respected again in search.
DBE-13090: View DDL from data works again.
DBE-5341: Go to related symbol has been added to the context menu of the object in the code editor.
DBE-4960: [PostgreSQL] Go to related symbol works for navigating from triggers to the related procedure, and vice versa.
DBE-13033: Navigation by foreign keys supports references to one column.
DBE-13037: Scroll from editor works from the data editor.
DBE-12967: [SQlite] Full-Text Search uses LIKE to search within LONGVARCHAR fields.
Data viewer:
DBE-5435, DBE-11780, DBE-12827, DBE-11591: Fixed some bugs with missing ctid columns.
DBE-13150: The data diff viewer works again.
DBE-13126: Text search works when invoked a second time.
DBE-12985: [MySQL]: The default value for the date field is now correct.
DBE-12940: The Toggle Soft-Wrap and Toggle Formatting buttons don’t disappear anymore.
DBE-12594: Formatted mode for XML no longer removes all spaces.
Code generation:
DBE-8654: Run routine generated code contains qualified objects.
DBE-12934: Argument direction is taken into account when modifying the routine.
DBE-12873 [BigQuery] Int64 is the default type when creating a new column.
DBE-12892 [BigQuery] Dropping views now works.
Code highlighting:
DBE-9813: [Clickhouse] Support for CREATE DICTIONARY.
DBE-12996: [Clickhouse] Support for EXISTS (database | dictionary | view) statements.
DBE-12993: [Clickhouse] Correct syntax highlighting for CREATE OR REPLACE.
DBE-12994: [BigQuery] Support for EXPORT DATA, TABLESAMPLE SYSTEM, CREATE SCHEMA, ALTER SCHEMA, and DROP SCHEMA.

New in DataGrip 2021.1.1 Build 211.7142.37 (Apr 29, 2021)

New in DataGrip 2021.1 Build 211.6432.6 EAP 3 (Mar 11, 2021)

New in DataGrip 2021.1 Build 211.6085.17 EAP 2 (Feb 19, 2021)

New in DataGrip 2021.1 Build 211.5538.21 EAP (Feb 5, 2021)

Connectivity:
We’ve reworked the connection window to make it more friendly:
Drivers and data sources are now listed on two different tabs. The list of drivers won’t bother experienced users, while newcomers will not confuse them with data sources.
Every driver’s page includes a Create data source button.
The Test Connection button has been moved to the footer so that you can use it from any tab of the data source properties, not only the General and SSH/SSL tab as before.
The DDL data source properties page has a drop-down list for choosing the dialect.
The JDBC URL field can be expanded if the URL is really long.
Grants:
We’ve added a UI for editing grants when modifying objects.
Editing grants per user will come in one of the next EAP builds.
Data editor:
Sorting:
We’ve improved the sorting of data:
We added the ORDER BY field, and it works similar to the WHERE field (which was Filter field before): enter a working clause to have it applied to the query of the grid.
The sorting is not ‘stacked’ by default. This means that if you click on a column name to sort data by, the sorting based on other columns will be cleared. If you would prefer to use stacked sorting, click a column name while holding the Alt key.
If you want to use sorting on the client side (DataGrip will not rerun the query nor sort the data within the current page), uncheck Sort via ORDER BY.
It’s also possible to open tables with predefined sorting based on the numeric primary key.
Export:
When you copy binary data that hasn’t been completely loaded yet, the following notification will be shown
If you don’t want the data to be truncated, increase the value in Settings/Preferences | Database | Data Views | Maximum number of bytes loaded per value.
When you export to Excel, the resulting file will contain the query on a separate sheet.
Import:
When you import a CSV file, the option to clarify that the first row is a header is now available in the context menu as shown below
Transposing:
Now there is an option to always transpose the result if it contains a single row.
Database explorer:
The default layout of the database explorer has been changed, with non-major objects now available under a dedicated node. Most of the time people work with tables, views, and routines, whereas seeing users, roles, tablespaces, foreign data wrappers, and many other types of objects is not high on their list of priorities. So, these secondary objects are now hidden under two nodes, Server Objects and Database Objects.
Also, for Oracle there is an option to show or hide auto-generated objects in the tree, including the following:
Materialized view logs
The underlying tables for materialized views
Secondary tables
New types of objects – functions, modules, and virtual columns – are introspected for SQLite.
Queries parsing for unsupported databases:
We’ve introduced a new setting for using unsupported databases. When working with these databases in DataGrip, you’ll need to use either the SQL:2016 or Generic dialect. Generic is almost identical to SQL:2016, with the only difference being that all found errors are not highlighted.
To access the setting, go to Preferences | Database | General | Split a script for execution in Generic and ANSI SQL dialects. The following values are available to choose from:
On valid ANSI SQL statements or by separator – this is the default setting that is suitable for the majority of cases. In other words, we’ll do our best to understand what you want to run.
On ANSI SQL Statements – split statements as before. The logic is based only on what DataGrip considers valid based on SQL:2016 grammar.
By statement separator – extract and run statements by separators. Use it if the first option didn’t do the job. For GenericSQL, the separator is a semicolon. Please note it is no longer possible to set a custom separator.
Here are some of the problems we’ve resolved:
Many users have reported a problem with running CTEs. This should have been partially mitigated when Generic grammar was upgraded from SQL:92 to SQL:2016, but On valid ANSI SQL statements or by separator option still helps with complex CTEs. Another example of the statement which will work with this option is the unusual MERGE statement.
The On valid ANSI SQL statements or by separator option also helps run things that aren’t statements at all in SQL:2016 grammar, such as for example show databases;.

New in DataGrip 2020.3.2 Build 203.7148.68 (Jan 28, 2021)

New in DataGrip 2020.3.1 Build 203.6682.134 (Dec 24, 2020)

New in DataGrip 2020.3 Build 203.5981.102 (Nov 26, 2020)

New in DataGrip 2020.3 Build 203.5784.29 EAP 4 (Nov 12, 2020)

New in DataGrip 2020.3 Build 203.5251.28 EAP 3 (Oct 22, 2020)

SQL for MongoDB:
TL;DR – You can now use SQL to query MongoDB databases.
Only SELECT queries work.
Working сlauses: JOIN, WHERE, GROUP BY, HAVING, ORDER BY, LIMIT, OFFSET.
SELECT:
Options you can use: DISTINCT, ALL.
You can use aggregate functions: AVG, SUM, MIN, MAX, and others.
Columns can be qualified.
Restrictions:
COUNT (expression) is not yet supported.
You can’t use aggregate functions, such as AVG, SUM, MIN, and MAX, as if they were not aggregate. For example, SELECT MAX(1,2,3) won’t work.
FROM:
Nested SELECT statements are supported.
You can use aliases for tables.
You must use an alias for a nested SELECT statement. An inspection will display a warning.
Restriction:
Aliases must not contain dots.
JOIN:
Only JOIN (INNER JOIN) and LEFT JOIN (LEFT OUTER JOIN) are supported.
Only the ON condition is supported. USING doesn’t work.
You can only use one condition at a time.
You can only use the `=` operator in the ON condition. `==` also works.
Restrictions:
Nested SELECTs are not supported in JOIN clauses.
Table names and aliases shouldn’t be duplicated in all JOIN clauses.
WHERE:
Supported operands: =, ==, >=, <=, >, <, <>, !=, +, -, /, *, %, AND, OR, NOT, LIKE, NOT LIKE, IS, IS NOT, IN, NOT IN, BETWEEN, NOT BETWEEN.
LIKE requires a string literal. You can use the classic wildcards for the LIKE operator; they will be translated into the valid regular expression for MongoDB.
GROUP BY, HAVING, ORDER BY:
You can use aggregate functions: AVG, SUM, MIN, MAX, and others.
Data types:
You can use:
String, Integer, Float, Boolean
NULL, NAN, INFINITY
Arrays and maps
Functions:
You can use all available MongDB functions except map, reduce, filter, and let.
Some functions in MongoDB, such as dateToString, require named arguments. To use them, please use a PostgreSQL-like syntax for the named parameters, using ‘=>’ or ‘:=’. You’ll get an error if you don’t specify names for the parametrized functions, and vice versa.
Object builders:
The following object builders can all be used: BinData, HexData, UUID, MD5, ObjectID, Date, ISODate, Code, DBRef, RegExp, NumberInt, NumberLong, NumberDecimal, Timestamp, MinKey, MaxKey.
Regardless of whether you use them with the new keyword, we’ll add it to the actual MongoDB query. The only time we won’t do so is when you use the Date object builder, because in this case it matters.
If we don’t know whether you are using a function or an object builder, we consider the usage to be a function call if the new keyword is not present, and we take it to be an object builder if the new keyword is present.
Behind the scenes:
Want to know what will be sent to the MongoDB database? There are two options in the context menu: Copy JS script to clipboard and Show JS Script. In the JS Script Preview window you can edit the query and run it.
That’s it! We are looking forward to receiving your feedback, and we hope our 2020.3 release will help you work with MongoDB!

New in DataGrip 2020.3 Build 203.4818.41 EAP 2 (Oct 15, 2020)

New in DataGrip 2020.3 Build 203.4203.31 EAP (Oct 1, 2020)

New in DataGrip 2020.2.3 Build 202.7319.56 (Sep 17, 2020)

New in DataGrip 2020.2.1 Build 202.6948.45 (Aug 19, 2020)

New in DataGrip 2020.2 Build 202.6250.6 EAP 3 (Jul 7, 2020)

New in DataGrip 2020.2 Build 202.5792.39 EAP (Jun 19, 2020)

Separate editor for cell values:
Now if you have a huge value in your cell, it can be viewed or edited in a separate panel. You can also toggle soft wrap mode using the right-hand toolbar.
DML preview in the data editor:
Starting with this version, you can review the query that represents your changes in the data editor. This query is not the exact SQL that will be run to modify your data, because DataGrip uses a JDBC driver to update tables, but most of the time it will be the same.
Export to the clipboard in the context menu of the data editor:
After we introduced a dialog window for exporting data, one tiny scenario became more complicated, namely, exporting the whole result or table to the clipboard. So, we’ve added the following item to the context menu.
Even better JOIN completion:
One fewer step to complete the JOIN clause: now we offer the whole clause when you start typing ‘JOIN’.
Native libraries in the driver settings:
Now you can specify the path to any native library for the driver. Here are just a few situations where this can be useful:
In SQL Server, you can specify the mssql-jdbc_auth-<version>-<arch>.dll for the SSO authentication if you manually set up the driver. By default, SSO authentication works out of the box.
In an Oracle database, you can specify the ocijdbc library to use the OCI driver.
In SQLite, you can specify the runtime loadable extensions to make it easier to use them from the query console: no need to specify the full path.
All databases and schemas in the database tree:
DataGrip will only show the databases and schemas you have chosen to be displayed. While this can be useful if you have many databases and schemas, it also defines which schemas need to be introspected, as DataGrip loads the metadata from the database and makes use of it later.
However, some people are more used to the tools in which they always see all the available databases and schemas. They also prefer externally added schemas to appear in the database explorer after a refresh.
This is why we’ve added a new option to the database explorer: Show All Namespaces. In this mode, databases and schemas that are not introspected are in grey.
Basic support for Oracle DB links:
Now Oracle DB links are shown in the database explorer, and the code which uses them is correctly highlighted.
Run configurations for *.js files:
If you have MongoDB scripts, you can create Run Configurations from them.

New in DataGrip 2020.2 Build 202.5103.3 EAP (Jun 3, 2020)

A new UI for boolean values:
Well, this is quite a welcome development! There’s a new way to observe and edit boolean values that is more user-friendly.
Editing:
The space key toggles values like it used to.
Typing f, t, d, n, g, or c will input the corresponding values: false, true, default, null, generated, and computed. We’re all lucky that all these words begin with different letters!
Typing anything else will open the drop-down with possible values.
A new UI for cropped data:
Sometimes DataGrip cannot load all the data for a given cell. This happens if the size of the data in the cell is larger than allowed by the Database | Data views | Max LOB length setting. In these cases, we used to add a small piece of text, like “10 KB of 50 KB loaded”, to the value. Now instead of altering the value, we just show a hint.
Long tabs: no more:
Another usability issue that won’t annoy you in 2020.2: long tabs.
Introduce variable:
This refactoring is now supported in more dialects: SQL Server, Db2, Exasol, HSQL, Redshift, and Sybase. You can introduce variables from any expression that has the simple type.
UI for creating views:
While we are always advocating for people to use the Generate functionality (Alt+Ins or Cmd+N in the SQL editor) if they want to create a view, many are more comfortable using the UI. We heard you, and we’ve added a UI option for that.
Refresh database quick-fix:
Sometimes you have unresolved objects in your script. When you do, DataGrip doesn’t understand where these objects are located and suspects that they don’t exist at all. While in many cases this is true, sometimes the objects are unresolved because you just need to tweak the context you are working on.
We’ve added the Refresh database quick-fix, which will help you if an object has been added to the database from somewhere else since the last time you refreshed your database.
Better filtering for MongoDB:
In addition to ObjectId and ISODate, filtering now supports UUID, NumberDecimal, NumberLong, and BinData. Also, if you have a valid UUID/ObjectId/ISODate in your clipboard, you will see this value in the offered filters.
We’ve also added regular expressions to filtering, in case you are missing the LIKE filter from MongoDB.
Other improvements:
In the data editor, if you edit a one-line string value, the down/up keys will finish editing it for you
In the event you are experiencing network issues, introspection in Oracle databases is now faster than it was before
The XML extractor is now a little bit better: If the original value is already XML, the extractor will not wrap it again in the extracted XML. If the value is not already XML, then special characters ‘<‘ and ‘>’ will be converted to xml entities: < and >

New in DataGrip 2020.1.4 Build 201.7846.70 (May 29, 2020)

New in DataGrip 2020.1.3 Build 201.7223.85 (Apr 30, 2020)

New in DataGrip 2020.1.2 Build 201.6668.164 (Apr 22, 2020)

New in DataGrip 2020.1 Build 201.6668.99 (Apr 6, 2020)

New in DataGrip 2020.1 Build 201.6668.74 RC (Apr 2, 2020)

New in DataGrip 2020.1 Build 201.6668.27 EAP 4 (Mar 26, 2020)

New in DataGrip 2019.3.4 Build 193.6911.16 (Mar 17, 2020)

New in DataGrip 2020.1 Build 201.5985.27 EAP (Feb 27, 2020)

New in DataGrip 2019.3.2 Build 193.6494.42 (Feb 13, 2020)

New in DataGrip 2019.3.2 Build 193.6015.44 (Jan 22, 2020)

New in DataGrip 2019.3 Build 193.4386.21 EAP (Oct 25, 2019)

New in DataGrip 2019.2.2 Build 192.6262.49 (Aug 16, 2019)

New in DataGrip 2019.2 Build 192.5728.16 EAP 3 (Jul 12, 2019)

New in DataGrip 2019.2 Build 192.5587.22 EAP 2 (Jul 3, 2019)

New in DataGrip 2019.2 Build 192.5281.18 EAP (Jun 20, 2019)

Services tool window:
All our IDEs now have a new tool window called Services. In DataGrip, you can observe and manage all the connections there.
Every connection has its own node under the corresponding data source. If the small green light on the icon is on, it means that the connection is alive. You can close any of them.
You can view all the service types as nodes, or you can alter the view to see them as tabs. Use the Show in New Tab action from the toolbar or simply drag and drop the needed node on to the edge of the Services tool window.
The query result is now attached to the particular console under its connection in the
Service view. We realize that the UI has changed a bit, so please provide us with feedback. During the EAP there is still the chance to test and apply changes quickly. For now, if you want to have more room for the results, change the size of the left panel.
Query live timer:
The Services tool window also provides you with some very requested functionality: a query live timer. As you can see, to the right of every connection which runs a query there is information about the time it has taken.
Full-text search:
Now there is the ability to search for some data even if you don’t know where it is located. To do this, select the data sources or groups of data sources you want to search through and invoke Full-text search from the context menu. There is a shortcut as well: Ctrl/Cmd+Alt+Shift+F.
Then you will see the dialog you should put the string you need into. Here you can see the list of data sources to search through and also define some options for the search.
As soon as you have started the search, DataGrip performs queries against all the tables and views in these data sources. These queries just search for the string using the LIKE operator.
After clicking on the result, the data editor will open. The filter will be pre-defined to give you only those strings where the data is found. If you cannot locate the data because of the number of columns, use text search in the data editor: Ctrl/Cmd+F.
Filtering by a data source in search and navigation:
When you are locating an object in the GoTo pop-up, sometimes many similar objects are present in the list. It frequently happens when you have many mirrors: production, staging, test, etc.
In DataGrip 2019.2, you can choose where to search: in a particular data source or in a group of them.
The same works for Find In Path which is extremely useful when searching for source code inside of DDLs of other objects.
Code analysis:
First, we integrated a quick-fix into the inspection tooltip. Now, if DataGrip knows how to fix the problem, you will know about it by just hovering the mouse over the warning. To fix the problem just click on the link at the bottom left corner of the tooltip or press Alt+Shift+Enter.
Unnecessary usage of CASE:
When you use CASE construction DataGrip analyzes whether they can be transformed into more readable ones.
Possible truncation of the string:
DataGrip detects the length of the string when assigning a value to the variable and warns you if it will be truncated.
Database tree view:
Quick backup of the table:
It was possible to copy tables via drag-n-drop, but it didn’t work when copying to the same schema. In fact, this could have been very handy if you ever needed to create a quick backup of the table before any crucial data manipulations. So we’ve now made it work!
Live connections:
From 2019.2 the small green light indicates if there is an alive connection to the data source.
Table comments:
If you wish to see comments of the tables in the tree view toggle View | Appearance | Descriptions in Tree Views option.
Miscellaneous:
New option to control the behavior of Move Caret to Next Word:
The default behavior of the Move Caret to Next Word action is changed: the IDE will move the caret to the end of the current word.
To change the behavior of the caret movement actions, go to Preferences/Settings | Editor | General.
People usually perform this action by pressing Ctr+Arrows on Windows and Linux and
Opt+Arrows on Mac. It has different default behavior in different operating systems. In Datagrip we used Windows-like behavior and we changed it to the Mac-like one.
Editable columns in Cassandra:
In Cassandra now you can edit these types of columns: set, list, map, tuple, udt, inet, uuid, and timeuuid.
Other:
The upcoming DataGrip 2019.2 will run under JetBrains Runtime 11, the uncertified fork of OpenJDK 11, by default.
Jump outside closing bracket/quote with Tab option is enabled by default.
Surround a selection with a quote or brace option is enabled by default.
Introduce alias action is added to the refactoring menu.
DataGrip works with PostgreSQL 12: DBE-8384.

New in DataGrip 2019.1.2 Build 191.7141.30 (May 1, 2019)

New in DataGrip 2019.1.1 Build 191.7141.8 (Apr 28, 2019)

New in DataGrip 2019.1 Build 191.6707.12 (Apr 4, 2019)

New DBMS support:
In this release cycle, we focused a lot on supporting several new databases.
Greenplum is an analytics database based on PostgreSQL. It is currently developed by Pivotal and the open source community.
Vertica is column-oriented storage designed to handle large volumes of data.
Apache Hive is a data warehouse built on top of Apache Hadoop for providing data query and analysis.
Snowflake is a cloud-based data-warehouse. In 2019.1 DataGrip supports only SQL dialect, the introspection support comes later.
Connection dialog:
General:
We’ve re-arranged the fields here to make the connection process more user-friendly.
The Connection type field is what used to be URL type. It determines the whole UI of this dialog, which is why it’s now on top along with the driver chooser.
The Database field goes after the credentials because sometimes credentials are needed to provide the database list. The list should be invoked by Ctrl+Space
Password saving is now implemented via a drop-down. It has four options: Never, Until restart, For session, and Forever. For Session is probablythe only option that requires some explanation: it will save your password until you disconnect from the data source.
Options:
We’ve moved Read-only, Auto-Sync, and Transaction control settings here, from the General tab.
Newly introduced settings:
Run keep-alive query each N seconds will help you keep the connection alive. You can define the custom query in the driver settings for unsupported databases.
Auto-disconnect after N seconds. Pretty self-explanatory.
Startup script is an SQL query which will be run each time you establish a connection. Remember that if Single connection mode is unchecked, each new consolecreates a newconnection.
Renamed setting:
Warn if editing an outdated DDL is the new name for what used to be Notify when the outdated object is opened.
Schemas:
Object filter has been transferred here from the Options tab.
Data source list:
A small enhancement: DDL data sources now have their own group in the data source list inside the connection dialog.
Search and navigation:
Recent Locations:
There’s a new Recent Locations popup that lists your recently visited/changed code locations. It presents them as code snippets with a couple of lines before and after thelocation.
This popup was inspired by Recent Files, but with an ability to search by visited code locations. This should come in handy when you remember what the code was about butcan’trecall where it’s located. Especially if you work with several query consoles: they usually have similar names!
Press Delete/Backspace to remove locations from the popup.
The default shortcut for this popup is Ctrl+Shift+E.
Find in path:
DataGrip can search in source codes of the objects. This was available only if you chose the All Places scope. We’ve cleaned up this UI a little bit and removed the Module and Project tabs.
A new scope, Attached Directories, is available. Use it if you want to search through files in the Files tool window.
Go-to popup:
All navigation actions now work from here.
For instance, if you’re searching for a table, see what you can open from right here:
Table’s DDL: Ctrl+B.
Table’s data: F4 (Enter does the same for tables).
Modify Table dialog: Ctrl+F6.
Locate in… popup: Alt+F1 (Use it to see the object in the database tree view).
Quick doc popup: Ctrl+Q.
SQL generator: Ctrl+Alt+G.
Code insight:
Combined items in completion:
We’ve added some combined options to the completion list for CREATE and DROP statements. For example, when you start typing CREATE, you canselect CREATETABLE.
One more benefit is that you can use abbreviations!
New inspections:
Usages of GOTO statements and Named arguments should be used inspections are turned off by default as only some developers want these things to be reported.
Usages of GOTO statements inspection has three options:
Report all GOTO statements;
Report uses of GOTO statements to exit a loop;
Report backward GOTO statements;
Working with files:
Now there is a Default Directory option in Settings/Preferences | Appearance & Behavior | System Settings. It will define where your new project will be created by default.
Database tree view:
We’ve improved database introspectionfor IBM DB2. You should now see the following new objects in the database tree: trigger, method, module, data type, variable, condition, sequence,check constraint, role, and global temporary table.
We’ve also added icons for some databases we don’t support yet. Before, if you had many data sources of unsupported databases, they could all make a mess in the Database tool window. Wehope it looks a little bit better now.
Other:
Customizable themes:
This release adds the possibility to fully customize the appearance of the IDE as now you’ll have the power to design your own theme from scratch. We’ve created a few brand newthemes to get you started. They can be downloaded as plugins.
You can literally change the color of anything. Create your own theme plugin using the DevKit and modify the IDE appearance via a JSON file. Here are some links that you may finduseful:

New in DataGrip 2019.1 Build 191.6183.32 EAP 2 (Mar 15, 2019)

New in DataGrip 2018.3.4 (Mar 13, 2019)

New in DataGrip 2019.1 EAP (Feb 21, 2019)

New in DataGrip 2018.3.1 Build 183.4886.38 (Dec 19, 2018)

New in DataGrip 2018.3 Build 183.4284.162 (Dec 6, 2018)

Database objects:
Cassandra database:
First and most important, a new database has joined our family. We’re gradually finding our feet with NoSQL. After adding Clickhouse support in 2018.2.2, we have now added support for Cassandra.
Write queries, observe data, and generate scripts—do everything you like about DataGrip!
Generate SQL files for the selected objects:
Now, if you use the SQL Generator (Ctrl+Alt+G) to get the DDL from objects, you can also generate the SQL files for these objects. To do this, click the Save button on the left pane. As you can see, we’ve created two layouts for the output. Please, if you have any ideas you would like implemented, share them with us. Tell us what kind of settings you would like to see here.
Anyway, now you can click the Edit button to the right of the Layout drop-down and edit any of them. Or create your own. These layouts are just groovy scripts.
PostgreSQL extensions:
DataGrip now supports extensions in PostgreSQL.
Data source quick doc:
The quick doc for the data source (Ctrl+Q) now displays some statistics including the number of different objects.
Code completion:
Automatic aliases:
A new setting is available to automatically add aliases when completing table names. If the pre-generated aliases don’t suit your needs, feel free to create your own custom ones for particular tables.
Not aggregated fields in GROUP BY:
When you use the GROUP BY statement, DataGrip offers you a list of non-aggregated fields.
All columns list in SELECT:
A list of all columns is available in completion after the SELECT keyword. Also works for MERGE and INSERT INTO table variable.
Postfix completion:
We’ve also introduced Postfix completion which may be familiar if you’ve used other IntelliJ-based IDEs.
Named parameters:
Completion now works well for named parameters of stored procedures.
Context for ambiguous names:
In the case of ambiguous names, DataGrip now shows you the context.
Invert order of operands in JOIN:
A new setting is called Invert order of operands in auto-generated ON clause.
If it’s set to off, the FROM table will be the first in JOIN conditions.
Refactoring:
Introduce alias:
Introduce alias, one of the most important SQL refactorings, is finally here. Get your stop-watch ready and see how much time this saves you!
Extract subquery:
The name suggested for CTE doesn’t lead to conflicts: DBE-6496
Context is properly defined if a statement is wrapped in another expression: DBE-6503, DBE-6517
DataGrip won’t suggest extracting CTE when the column aliases in an as-expression for dialects that don’t support it: DBE-6490
This refactoring is enabled for MySQL: CTEs are supported since MySQL 8
This refactoring works OK with deep subqueries. DBE-7332, DBE-7333
Code insight:
Unsafe statements
DataGrip will now warn you if you use the DELETE or UPDATE statement without WHERE clause.
If you are running this, there will be a cautionary notice.
Unreachable code:
Another small improvement is a new inspection called Unreachable code.
Unused subquery:
We’ve added a new inspection, Unused subquery item. It will help make your code neater.
Code generation:
Dialects for Live Templates:
Now you can choose dialects for Live Templates. Once a dialect is selected for a live template, it will only work in the specified dialect.
This option lets you create different dialect-based implementations for the same abbreviation.
Say, we want to create a template for getting the first n rows. In SQL Server and PostgreSQL, this query would have different syntax. You can use the same abbreviations for different live templates if they are in different groups. Create two new groups: SQL Server and PostgreSQL. In each group, create a corresponding live template with the appropriate syntax.
CREATE TABLE definition for SELECT:
It is now possible to add a CREATE TABLE definition from the SELECT query. Just write an INSERT statement before it, and then press Alt+Enter → Create table definition
Column names hint:
Column names hint appears automatically when using INS live template
Connectivity:
Single connection mode:
Previously, each new query console meant a new connection. In the new version, it’s possible to work with just one connection for the data source and have all consoles use that same one connection. In fact, it allows you to see the temporary objects in the database tree, or use the same transaction in different consoles. This is our first step toward creating full connection management in DataGrip. To turn it on, go to Data source properties → Options → Single connection mode.
Auto-reconnect:
Also, the long-awaited auto-reconnect feature has been added, so disconnections after timeouts are no more!
Search and navigation:
New Search Everywhere:
IntelliJ Platform introduces a new better way to navigate over the project and the IDE: the reworked Search Everywhere dialog. In fact, it incorporates all of the other navigation dialogs: Search Everywhere, Find Action, Go to table/view/procedure/, Go to file, and Go to symbol. Note that all these navigation dialogs are still accessible through their own keyboard shortcuts, as before. To switch between tabs, use Tab.
Multiline code search:
Now it’s possible to perform search/replace for a multiline fragment in Find in Path / Replace Path dialogs. It’s easier now to find a query in your scripts or source codes.
Multiline TODO comments:
The IDE now supports multiline TODO comments. Now the first and all subsequent TODO comment lines are highlighted in the editor and listed in the TODO Tool Window. Add an indent starting from the second line of your multiline TODO comment, and the IDE will differentiate it from an ordinary comment.
User interface:
High-contrast color scheme:
Across all of our IDEs, we’re rolling out the brand new High-contrast scheme. To turn it on, press Ctrl+`go to Look and Feel, and then choose High Contrast.
Color settings:
We’ve also added the ability to define colors for data sources to the Properties dialog.
Better UI for page size setting:
We've also reworked the UI for the page size a little. Now there’s a simple way to see all the rows from a table or a result.
Minor stuff:
Code completion for:
Window functions
Numeric fields in SUM() and AVG()
FILTER (WHERE…) clause
Field types in SQLite
Items in brackets
Table value types
Use drop cascade syntax option when dropping an object.
Tons of fixes in SQL formatter. If your case isn’t covered yet, create an issue.
Expression/declaration lists can be folded in the editor
Ability to assign shortcuts for selecting tabs. IDEA-68324
Support for stored procedures in PostgreSQL 11. DBE-6863
Support for vector valued updates in SQLite. DBE-4449
If JOIN has no condition, this error is highlighted. DBE-6759
‘@’symbol doesn’t break the spell checker and thus works in variable names. DBE-2250
JSON groovy extractor works OK with big numbers. DBE-7019
Row count works if columns are sorted. DBE-2444
The correct search path is set in the reopened data editor. DBE-7044
Query plan visualizer works in Redshift. DBE-7129
Better alias suggestions for temp tables in SQL Server. DBE-5981
Columns of returned table are resolved in the code. DBE-7176
No more exception during synchronizing MySQL 5.7. DBE-7234

New in DataGrip 2018.3 Build 183.4284.159 EAP5 (Nov 26, 2018)

New in DataGrip 2018.3 Build 183.4284.109 EAP4 (Nov 16, 2018)

New in DataGrip 2018.3 Build 183.4139.19 EAP3 (Nov 1, 2018)

New in DataGrip 2018.3 Build 183.3975.10 EAP2 (Oct 25, 2018)

New in DataGrip 2018.2.1 Build 182.3911.26 (Aug 3, 2018)

New in DataGrip 2018.2 Build 182.3684.106 (Jul 26, 2018)

SQL Log:
First, now you’ll see every query that DataGrip runs in the console output. Whether it’s your SQL or something DataGrip needs to run internally, check the Output tab to understand what’s going on.
Second, literally all queries from the IDE are now logged in a text file.
New SQL formatter:
Thanks for sharing your ideas about SQL styles with us! We hope that now DataGrip will be able to accommodate many more different code styles.
The new SQL formatter is a feature we strongly need feedback on, so please try it out and if your specific cases are not covered, do let us know. We are still working on new clauses to add.
As you may already know, you can create custom Code Style schemes. Now any of them can be used specifically for each data source. To do this, go to the Options tab of the data source properties.
Running stored procedures:
This long-awaited feature has been implemented for Oracle and PostgreSQL! Support for SQL Server procedures is only available in DataGrip for now, but will soon appear in the 2018.2.1 updates of other JetBrains IDEs.
Source code migrations:
Now, to update the source code of any other objects, just double-click them and make the needed changes. The gutter (the vertical bar to the left of the text editor) will highlight the changes you’ve made. Note also the new Submit button on the toolbar.
Query plan diagram:
A diagram-based view is now available for the query plan. To view it, click the Show Visualization button on the toolbar after you invoke Explain Plan. As a reminder, it’s also available in the context menu for queries in the SQL console.
SQL editing:
Context info:
When editing a huge procedure in a package, it is sometimes useful to refresh your memory on its context, i.e. what particular procedure or package is now being edited.
Jump outside closing bracket/quote with Tab:
Starting with this version, you can navigate outside the closing brackets, or closing quotes, by pressing Tab. Note this works only when inputting parameters or values for the first time.
Data editor:
Column comments in tooltips
Number of selected rows:
Now DataGrip shows the number of rows selected in the data editor. Look for this in the status bar.
UI upgrades:
Touch Bar support:
We’ve added support for the MacBook Touch Bar. It only has an Execute button by default.
Assign a shortcut from Find Action:
Previously, it was impossible to assign a shortcut from the Find Action if using the Default keymap. We’ve fixed this bug and now it works in any keymap and any layout. A good reason to remind you that it’s possible!
Custom data source:
Now you can add custom data sources based on jdbc-driver. Click the + button on the toolbar and select the appropriate item from the drop-down.
Run SQL on a schema:
Before, the only way to run the script was by executing it from the context menu of the corresponding SQL file. Now you can use a more intuitive way: choose the datasource or the database you need and select Run SQL script from the context menu.
Dialect and console choosers:
Now you can choose the dialect of the SQL file and attach any console to it just from the toolbar.
Dark window headers:
Now you can make the Darcula theme even darker. If you are on a macOS, to darken the title bars, just go to Preferences → Appearance & Behavior → Appearance and select Use dark window headers.
Important bug fixes:
DBE-6681: MySQL comments are being formatted properly.
DBE-5204: DDL for a table opens in a right place.
DBE-1858: Deleting the criteria from the Filter field shows all rows in the data editor.
DBE-6436: Backspace doesn’t break quick search in Structure View.
DBE-6362: Views with no schema binding in Redshift are shown in the database tree.
DBE-6469: Record count in data editor works if sorting applied.
IDEA-189650: IDE opens empty files after restart.

New in DataGrip 2018.2 Build 182.3684.85 RC (Jul 24, 2018)

New in DataGrip 2018.2 Build 182.3569.14 EAP (Jul 5, 2018)

New in DataGrip 2018.2 Build 182.3341.22 EAP (Jun 21, 2018)

New in DataGrip 2018.1.4 Build 181.5087.33 (May 23, 2018)

New in DataGrip 2018.1.3 Build 181.5087.19 (May 18, 2018)

New in DataGrip 2018.1.2 Build 181.4892.10 (Apr 30, 2018)

New in DataGrip 2018.1.1 Build 181.4668.2 (Apr 12, 2018)

New in DataGrip 2018.1 Build 181.4203.585 (Apr 3, 2018)

Data editor:
Data editor SQL log:
Now, while updating data you can see which particular queries DataGrip is running. We have nothing to hide!
IDE general enhancements:
Rename everything:
Starting with this version, we have challenged ourselves to be able to rename all the objects we support. Sequences in Oracle, events in MySQL, triggers in PostgreSQL, and many other objects can now be renamed by pressing Shift+F6. This works both in the database tree and in an SQL script. Remember that usages of the object in other scripts will also be renamed.
Schema switch mode:
Now you can tell DataGrip how to switch schemas.
Automatic: DataGrip can switch schemas during internal operations when defining the context. This is the default behavior for all databases except PostgreSQL.
Manual: DataGrip cannot switch schemas during internal operations when defining the context. However, you can switch them manually via the switcher in the top-right corner. This is the default behavior for PostgreSQL.
Disabled: If you work with pg_bouncer, no more wildcat switches!
Navigation:
We added an option called Prefer data editor over DDL editor.
This option affects:
Navigation to the table/view by Ctrl+Т/Cmd+O.
Navigation to the column by Shift+Ctrl/Cmd+Alt+N.
Double-clicking on the table/view or column in the database tree view.
‘Navigate references to DDL editor’ is now called Prefer database view instead of DDL editor. As you probably know, it defines where you’ll be taken when you click Navigate to declaration (Ctrl/Cmd+B or Ctrl+Click) from the SQL.
In DataGrip, you can now navigate to classes if you use any of the other supported languages.
In other JetBrains IDEs, you can finally see database objects here like tables, stored procedures, etc. Remember that there’s a filter by language.
Running scripts
Quick documentation for files:
We added quick docs for files. For example, now it’s much easier to know the file size. But that’s not all!
Database view:
We’ve added MariaDB to the list of supported databases.
We’ve merged two navigation actions: Go to class and Go to table.
DataGrip now supports external schemas in Redshift and virtual schemas in Exasol.
Events in MySQL are shown in the database tree. Source code generation is also available.
DataGrip now supports partitioned tables in PostgreSQL 10.
SQL editing:
Now DataGrip lets you navigate to the next or previous identifier occurrence by using two shortcuts, Alt + Wheel down and Alt + Wheel up. (Or, enter ‘highlighted element usage’ in Find Action.) Before, you could only navigate to the next text occurrence. It should be noted that text occurrence and reference are not always the same.
Another new action in DataGrip is Move element left or right. This works for different kinds of lists including parameters inside functions, fields in INSERT statement, and the column list. Note that it doesn’t spoil the comma while working with the column list, while Move Line would.
SQLite commands used to spoil highlighting. No more.
Completion for file references now works for Oracle and Exasol.
Common table expressions are supported in MySQL.
The Duplicate entire lines action now works at the end of the file as well. If you weren’t aware of what this action does, it duplicates all selected lines adding a line break before each one. In many cases, it’s much handier than just using Duplicate (Ctrl+Cmd/D).
The IDE now highlights the folded code regions that contain errors or warnings, and colors such blocks according to their validation status. The folded code also will be highlighted if it contains matching occurrences for the search results.
Other:
Features:
In the Replace in Path window, the IDE now lets you preview a regex replacement.
When you search through the current file, the IDE now highlights folded code regions if they contain the matching occurrences.
The REST client plugin is now available.
Code formatter doesn’t change keywords casing by default.
Fixes:
DBE-397: We don’t use driver-level read-only mode anymore. This will let you run safe statements that don’t begin with “s”.
DBE-5969: No error is raised when inserting a row with all default values.
DBE-5999: The ability to sort items in structure pane is added.
DBE-2102: Several fixes are delivered concerning default constraints in SQL Server. Now it’s possible to alter and delete them.
DBE-5968: Sybase shows the correct lengths for nchar, nvarchar, unichar, and univarchar types.
DBE-4962: Cascade rules of foreign keys are now correctly displayed for SQL Server.
DBE-6028: Code folding works with CTEs.
IDEA-124160: Now, the Search Everywhere pop-up receives focus.

New in DataGrip 2018.1 Build 181.4203.581 RC (Mar 29, 2018)

New in DataGrip 2018.1 Build 181.4203.511 EAP 3 (Mar 22, 2018)

New in DataGrip 2018.1 Build 181.3870.22 EAP (Mar 14, 2018)

New in DataGrip 2017.3.7 Build 173.4674.7 (Feb 28, 2018)

New in DataGrip 2017.3.6 Build 173.4652.3 (Feb 22, 2018)

New in DataGrip 2018.1 Build 181.3870.22 EAP (Feb 21, 2018)

New in DataGrip 2017.3.5 Build 173.4652.2 (Feb 14, 2018)

New in DataGrip 2017.3.4 Build 173.4301.31 (Jan 17, 2018)

New in DataGrip 2017.3.3 Build 173.4127.18 (Dec 20, 2017)

New in DataGrip 2017.3.2 Build 173.3942.44 (Dec 15, 2017)

New in DataGrip 2017.3.1 Build 173.3942.40 (Dec 14, 2017)

New in DataGrip 2017.3 Build 173.3727.157 (Dec 6, 2017)

Please welcome DataGrip 2017.3, the third big update of 2017, packed with various enhancements. Let’s have a look what it has to offer!
Database tree view:
Group data sources:
Closing an old outstanding ticket with a number less than 100 is not a situation that we frequently find ourselves in; especially when it’s for such a long-awaited feature. We are happy to introduce you to our new feature: group data sources. Press F6 or choose Move to group… from the context menu.
Group is the attribute of the data source. Now you cannot create an empty group and add existing data sources to it. Please, us? New group as shown on the screenshot.
Managing schemas:
We replaced the Schemas… node in the database tree view with a lightweight hover option, which when used, will show the number of schemas currently displayed. Click on it to add or hide schemas.
It is also possible to use Context menu ? Database tools ? Manage selected schemas or you can simply press Alt+Enter on the data source.
New supported objects:
Users and roles are now displayed in PostgreSQL and AWS Redshift.
Foreign Data Wrappers and as a consequence, foreign tables, are now displayed in PostgreSQL.
Drag-and-drop multiple objects to the editor
Now you can drag-and-drop several objects from the database tree view to an editor.
Well, if you need all of them, then use the Expand wildcard with Alt+Enter, as it is definitely more suitable :)
SQL:
It is now possible to use the SQL generator to generate DDL scripts with options. To do this, press Ctrl/Cmd+Alt+G or choose Context menu ? SQL Scripts ? SQL Generator… and get the generated DDL of any kind of object (table, schema, procedure, whatever) or even several objects simultaneously.
The JOIN statement completion has become even smarter! It now offers you the variant with the complete clause
We have added PostgreSQL 10 grammar support.
If you are already using PostgreSQL 10 and you see any incorrect code highlighting, please report it to us.
Executing queries:
DataGrip will now prompt you to choose a database/schema along with a data source when you try to run an SQL file from the context menu.
Another similar enhancement we have made is that a list of data sources with related consoles will now appear when attaching the console to a file.
There was only one Execute action before; now there are three of them. Change the behavior, and assign shortcuts: they are all completely independent. For example, you can create an action which will execute the whole script, without having to choose the exact query from the script.
There is a small improvement made especially for those of you who don’t like to use a mouse to be able to choose the schema of the console or the search path schema. Now there is an action called Set Current Schema. You can invoke it from Find Action (Cmd/Ctrl+Shift+A).
Or just assign a shortcut! For example, Cmd/Ctrl+Up will enable you to switch the context for the query console.
That shortcut is assigned to Show navigation bar by default in the platform, do you really use the Navigation bar? If yes, try Recent Files with Ctrl/Cmd+E.
Connectivity:
Enhancements in SSH tunneling: this build of DataGrip supports:
Reading OpenSSH config files (~/.ssh/config ? /etc/ssh/ssh_config).
Showing dialogue for a One Time Password.
Using an SSH-agent and Pageant for authentication.
Also, we added support for the Exasol database.
Data Editor:
We were asked to implement pasting from Excel tables. Generally to do this, it means that we need the ability to paste data in a DSV format. In DataGrip you can define any format you want, or you can let the IDE detect the format automatically.
For better readability, the data editor now aligns the numerical data with the right-hand side of the column.
Before, DataGrip didn’t restore tabs after re-opening. It was inconsistent with our other IntelliJ-based IDEs and it was not so easy for people to adjust to. Performing many queries at the start is not the best idea, so now the tabs are restored, and you can load the data to the data editors manually.
And the last enhancement in this section: values of two or three cells can be compared in the Diff Viewer. Select them and press Shift+Ctrl/Cmd+D
Navigation:
In one of the minor updates to 2017.2, we introduced a new flow for navigation. To cover all of the possible use-cases, and for those who are used to the previous versions; in 2017.3, we have added the option Navigate references to DDL editor.
With the Auto-scroll from Editor option, you can set up several types of behavior by pressing Navigate to declaration (Ctrl/Cmd+B or Ctrl/Cmd + Click)
AutoScrollFromEditor:
Navigate references to DDL editor On
Auto-scroll from Editor On
You’ll be taken to the DDL of the objects; the objects will be highlighted in the Database View. Focus in the Editor.
Navigate references to DDL editor On
Auto-scroll from Editor Off
You’ll be taken to the DDL of the object; nothing will be highlighted in the Database View. Focus in the Editor.
Navigate references to DDL editor Off
This will enable the “Old” behavior. The object will be highlighted in Database View; the Editor tab will remain as it is. Focus in the Database View.
The context menu in the data source has also been upgraded. Choose Jump to Console and you’ll now have a menu which you will be able to use to quickly switch between consoles which have already been created.
DataGrip 2017.3 has the ability to replace the selected occurrences in the Replace In Path dialog.
Scratches and Consoles are not found in a separate tab anymore; they are now placed in Files.
Other:
Synchronize your settings across devices.
Time is always displayed in UTC.
Generating DDL on the tables node doesn’t include views anymore.
DDL generation in MySQL works with escaped quotation marks. But the fix can improve performance problems. See details.
All the attributes (except obj_file and ink_symbol) are generated in the function DDL for PostgreSQL.
Better PIVOT support.
Expand column list deals well with table aliases.
SQL extractors respect casing setting of the Code style
Ability to choose the current schema for custom database’s query console.

New in DataGrip 2017.3 Build 173.3727.37 EAP 4 (Nov 17, 2017)

New in DataGrip 2017.3 Build 173.3531.20 EAP 3 (Nov 2, 2017)

New in DataGrip 2017.3 Build 173.3302.20 EAP 2 (Oct 20, 2017)

New in DataGrip 2017.3 Build 173.2696.33 EAP 1 (Sep 30, 2017)

New in DataGrip 2017.2.2 Build 172.4155.28 (Sep 6, 2017)

New in DataGrip 2017.2.1 Build 172.3757.39 (Aug 10, 2017)

New in DataGrip 2017.2 Build 172.3544.109 (Jul 27, 2017)

New in DataGrip 2017.2 Build 172.3544.95 RC 2 (Jul 24, 2017)

New in DataGrip 2017.2 Build 172.3317.79 RC (Jul 18, 2017)

New in DataGrip 2017.1.5 Build 171.4694.58 (Jul 18, 2017)

New in DataGrip 2017.1 (Apr 9, 2017)

New in DataGrip 2017.1 Build 171.3780.53 RC (Mar 16, 2017)

New in DataGrip 2016.3 Build 163.5644.18 EAP (Oct 8, 2016)

New in DataGrip 2016.3 Build 163.4396.16 EAP (Sep 14, 2016)

New in DataGrip 2016.2.3 Build 152.2032.7 (Sep 14, 2016)

New in DataGrip 2016.2.2 (Sep 14, 2016)

New in DataGrip 2016.2 (Sep 14, 2016)