DataGrip 2021.2 is here! This is the second major update of 2021, and it’s packed with various enhancements. Let’s take a look at what it has to offer!
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.
It is now possible to generate a DDL data source based on a real one. The DDL files are created locally and the new data source is based on them. This way you’ll always be able to regenerate these files and refresh the DDL data source.
Let’s take a look at how this works.
We’ve added a new menu item, Dump to DDL data source, to the SQL Scripts context menu.
When the dialog opens, you need to specify the folder where the newly created files will be stored.
On the Generation tab, specify how these DDL files should be generated.
Finally, click OK to create the DDL data source.
The folder with the new files is automatically attached to your project.
In v2021.2, you can create objects in a DDL data source via the UI. The corresponding files will be created locally.
The following important features have been added to diagrams:
If you are looking for a particular revision in Local History, you can use text search for help!
DataGrip now tracks local changes for object source codes. It can be especially useful when working with procedures and functions.
Since every object's sources are stored in a file, all external changes are also considered as local changes. When you introspect your database, this file is refreshed.
You can use the Local History popup to keep track of any changes to a function or procedure. Note that all external changes are considered as one change if they happened within two runs of the introspection.
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, uncheck the Shorten Tab Titles option.
For a long time we had the Hide All Tool Windows action, which could be called by double clicking on a tab or pressing Shift+Ctrl+F12. 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:
Now it's possible to define which objects should be presented in the code completion list: objects only from the schema switcher (or the search path), from the current scope, or from all schemas.
This can be also managed by smart completion. Smart completion is invoked when you press the completion hotkey (usually Ctrl+Space) several times.
Fields and operators are now available in code completion for MongoDB. Read this post for more details.
Code completion for cross-database synonyms is now available.
Computed columns are taken into account when completing
statements – they are not included in the suggested item.
Table qualification in
JOIN completion works as expected.
The priority of
ASC/DESC inside an
ORDER BY clause has
GRANT/REVOKE statements works as expected.
Queries that use recursive common table expressions are now properly highlighted and can be run without being selected.
The common table expressions syntax, when the CTE name goes before the
keyword, is now supported.
No more false-positive alerts from the inspection that reports not-null arguments
DBE-13188: Oracle PL/SQL record type fields are resolved correctly.
DBE-10550: DB2 Table aliases are resolved correctly.
If you turn on the Separate Procedures and Function option in the database explorer settings (the gear icon), it will immediately take effect.
For SQL Server there are dedicated nodes for scalar and table functions. For PostgreSQL there is a node for trigger functions.
A new database tree option, Show Constraints and Triggers in the Schema, assigns triggers, keys, and indices their own individual nodes in the database explorer.
Why is this useful?
If you turn off the Sort Alphabetically option in the database explorer settings, natural sorting for objects will be applied.
Here’s what it looks like when Sort Alphabetically is off:
Here’s what it looks like when Sort Alphabetically is off:
...and when Sort Alphabetically is on:
CockroachDB will be fully supported in this release. DataGrip will no longer rely on JDBC-based introspection, but use the native one instead.
This is much faster than JDBC-based introspection. Also, role, deftype, and check constraint could not be introspected at all in the previous version. The full list of objects that are now introspected includes database, role, privilege, schema, sequence, deftype, table, view, mat view, index, column, and constraints. That partitions are not introspected yet is a known issue.
Some time ago, we announced a mechanism for creating virtual foreign keys. Now we’ve used this mechanism to cover pg_catalog with virtual foreign keys. This brings a couple of improvements.
JOIN completion helps you when querying system tables:
Second, you can navigate by data in system tables:
We added support for tablespaces, data files, and temporary files. They are now introspected:
They are also included in DDL generation:
This isn’t full support yet, because metadata is not available for objects in linked servers. Linked servers are shown in the database explorer, and the DDL for their creation can be generated.
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.
We recently introduced Alt+Click for additive sorting. But if you prefer using Click, you can customize this behavior:
You can now add columns to MongoDB collections. This action lets you add a new field to any document of a collection.
Delete column will delete data not only on the page that is being displayed, but also throughout the whole collection.
With the help of the UI data editor, you can now add and remove columns in CSV files.
When working in a data editor, you might sometimes use complicated clauses in
ORDER BY fields. If you want to continue
working with the resulting query, use a new action, Copy Query to Console,
under the gear icon. It opens the query in the default console.
To make the navigation faster, we’ve removed the First row option. No popup will be displayed, and you will be navigated to the table that shows all referencing or referenced rows.
If you have foreign keys pointing to objects in another schema and these objects have the same names, they will be displayed as qualified in the foreign keys navigation UI.
The size of the
ORDER BY field is saved.
DBE-13055: The time zone is always shown for values with a time zone.
DATE type values don’t display time if no time is set.
Filtering by the
DATE field is possible.
DBE-12716: DB2 Filtering by binary, blob, char for bit data, and varchar for bit data fields is possible.
When you finish an import, a link to the new table appears in the notifications.
The behavior of the navigation bar is now more straightforward – the Enter key always expands the node.
Before, the Enter key opened data for tables and opened consoles for data sources.
If you want to navigate from the object in the navigation bar rather than opening its node, you can use these navigation shortcuts:
Now when you are searching for a function, procedure, or operator, DataGrip shows the signature in the Go To window. This helps when you use overloading heavily.
Starting from this version, you can enjoy the fully localized UI of DataGrip in Chinese, Korean and Japanese. Localization is available as non-bundled language pack plugins, which can be easily installed to DataGrip. More than 1.5 mln users started using the partially localized EAP version of our language packs. Now you can enjoy the full localization experience!
In DataGrip, projects are now located by default in the same place as they are in all other IntelliJ-based IDEs – in the user’s home folder, inside the DataGripProjects subfolder.
Your project in DataGrip is a complex of your data sources, console and scratch files, and attached folders. They were previously stored in the configuration folder, meaning that each time you updated your IDE, the projects were copied, along with IDE settings.
This sometimes caused the data source list to become empty. This problem has been solved, and now DataGrip behaves consistently with other IDEs.
Because of errors in project migration, those who used the first EAP build might have lost their Favorites, Bookmarks, Run Configurations, or data about virtual foreign keys. To restore them, please migrate from the previous version again. The details are described here: DBE-13410.
These buttons make it easier to navigate in the Settings window and not get lost there.
We’ve added Advanced Settings as a new node in Preferences/Settings. It contains some use-case-specific options conveniently grouped by IDE tool. Most of the settings have been transferred from the Registry, though some of them are new.
A couple of notable settings:
A new Show Scratch Files action (found via Find Action: Cmd+Shift+A) shows a list of scratches with snippets in a popup. It has the same UI as the Recent Locations popup with speed-search and deletion.
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.