What's New in DataGrip 2018.1

Data editor

General enhancements

Schema switch mode

Now you can tell DataGrip how to switch schemas. The following settings are available:

— Automatic: DataGrip can switch schemas during internal operations when defining the context.
— Manual: DataGrip cannot switch schemas during internal operations. However, you can switch them manually via the switcher in the top-right corner.
— Disabled: If you work with pg_bouncer, no more wildcat switches!

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.

Running scripts

Now when you run the file against a data source, your choice is remembered for further runs.

Quick documentation for files

We added quick docs for files: press Ctrl+Q. For example, now it’s much easier to know the file size. But that’s not all!

Navigation

We added an option called Prefer data editor over DDL editor.
This option affects:
— Navigation to the table/view by Ctrl+N.
— Navigation to the column by Shift+Ctrl+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+B or Ctrl+Click) from the SQL.

We’ve merged two navigation actions: Go to class and Go to table. Shortcut: Ctrl+N
— 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.

Database view

We’ve added MariaDB to the list of supported databases.

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.

Data source color affects console files in the Files pane.

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.

Completion for file references now works for Oracle and Exasol.

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.

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+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 Improvements