JetBrains DataGrip Blog

Hello! This is the first minor update for 2018.1.

Use the Check for updates action to receive the latest update if you are working with IntelliJ DataGrip 2018.1.

If you don’t get a notification about new updates please check the Updates page in the Settings / Preferences dialog. Make sure that the Automatically check updates for option is enabled.

Another crucial fix: the scrolling in 2018.1 became laggy. No more!

And here is a list of the other improvements included in 2018.1.1

— A new action is introduced: Context menu of the object → Database tools → Modify Comment.
— DBE-5479: Explain Plan works in Redshift.
— DBE-5987: Now it’s possible to use \N as null text in data import.
— IDEA-186636: The keystrokes aren’t lost during freezing anymore.
— IDEA-188229: Clicking the Replace all option from the Replace in path dialog doesn’t cause the IDE to freeze.

Hello,

Please give a warm welcome to our new release, DataGrip 2018.1!

We thank all of the EAPers who have helped test all the new features added in this release. Let’s take a closer look at those.

Data editor
— SQL log
IDE general enhancements
— Rename everything
— Schema switch mode
— Enhancements in Navigation
— Target is remembered when running scripts
— Quick documentation for Files
Database view
— MariaDB support
— External schemas in Redshift
— Virtual schemas in Exasol
— Events in MySQL
— Partitioned tables in PostgreSQL 10
— Datasource color affects associated files
SQL editing
— Navigate to next/previous occurrence
— Move element left or right
— Completion for file references
— CTEs in MySQL
— Folded code highlighting

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

— 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

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

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.

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

To try these goodies out, get your 30-day trial of DataGrip today!
We’re always listening to your feedback on twitter, in our forum, and in the issue tracker. Rant, rave, and give us your improvement suggestions!
Your DataGrip Team
_
JetBrains
The Drive to Develop

Hello! Here is our Release Candidate for 2018.1!

A few more fixes in this build:

DBE-6115: Scroll from editor works if horizontal split is used.
DBE-3548: The sequence start number is correct in PostgreSQL.
DBE-6104: Drop multiple columns works in H2.
DBE-5081: The REST client plugin is now available.
DBE-3260: Default values are added in the SSH configuration for data sources.

The release is coming next week!

DataGrip team.

DataGrip 2018.1 EAP 3

Hello! Here is the new EAP build for DataGrip 2018.1.

Rename everything

From 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 now can be renamed by pressing Shift+F6, regardless of whether it is done in the database tree or in the SQL script. Remember, that usages of the object in other scripts will also be renamed.

Enhancements in 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 know, it defines where you’ll be taken to when you click Navigate to declaration (Ctrl/Cmd+B or Ctrl+Click) from the SQL.

Important fixes:

— DBE-397: We don’t use driver-level read-only mode anymore. It will let you run safe statements that don’t begin with “s” symbol.
— DBE-6042: Support for partitioned tables in PostgreSQL.

That’s about it! Thank you in advance for trying our EAP builds.

Your DataGrip Team.

DataGrip 2018.1 EAP 2

It’s time for a new EAP build for DataGrip 2018.1. Let’s have a look at what it brings.

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

Data source color affects console files in the Files pane.

Also, there are several important bug-fixes:

DBE-5960: Window functions are supported for MySQL.
DBE-5969: No more error 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 connected with default constraints in SQL Server. Now it’s possible to alter and delete them.
DBE-5968: Sybase shows correct length 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.

That’s about it! Thank you in advance for trying our EAP builds.
Your DataGrip Team.

Hi! Another minor update for 2017.3:

— DBE-5904: The names of folders with console files don’t contain GUIDs anymore.
— Fixed additional issues with scrolling diagrams.
— Built-in SSH executable now supports strong cryptographic algorithms.

Your DataGrip Team
JetBrains
The Drive to Develop

Hi! Another minor update for 2017.3: we try to deliver important fixes as soon as possible :)

— DBE-5932: Deleting tables generates DROP CONSTRAINTS if needed.
— DBE-5745: DataGrip now correctly qualifies objects while deleting them in SQL Server and Sybase.
— New types added to the introspection: point, line, lseg, box, path, polygon, circle.
— Scrolling in diagrams works again, thanks to Lewislg who reported it in our forum!

Your DataGrip Team
JetBrains
The Drive to Develop

Yes, it has finally happened! :) We hope that in the next month you’ll use our early builds and share your feedback with us. As usual, our issue tracker, twitter and forum are open for you.

Let’s have a look at the goodies inside this EAP.

Data editor SQL log

Now, while updating data you can see which particular queries DataGrip is running. We have nothing to hide!

Connectivity and introspection

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. 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: if you work with pg_bouncer, no more wildcat switches!
— Disabled: Note that manual switching is also disabled in this mode.

We’ve added MariaDB to our 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. Icons will be delivered soon :)

SQL editor

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 kind 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 surely would.

Completion for file references now works for Oracle and Exasol.

SQLite commands used to spoil highlighting. No more.

Common table expressions are supported in MySQL.

Navigation
We’ve merged two navigation actions: Go to class and Go to table.

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

IntelliJ Platform enhancements
— In the Replace in Path window, the IDE now provides an ability to preview a regex replacement.
— Now, the Search Everywhere pop-up receives focus (IDEA-124160).
— When you search through the current file, the IDE now highlights folded code regions if they contain the matching occurrences.

That’s about it! Thank you in advance for taking these EAP builds for a spin. Do let us know what you think!
Your DataGrip Team

Hello! Here is the new bug-fix update for 2017.3.

There is even a new feature in the release: object filter. Define which objects you want to see in the database tree.

The most important bug-fixes are:

— Code completion respects number input: DBE-4965
— Paste from CSV format is now correctly detected
— New types of fields are available for editing in PostgreSQL: point, polygon, line, lseg, box, path, circle, pg_lsn, tsquery, tsvector

DataGrip lets you run scripts against the selected schema objects. For example, you can generate Java classes from tables or, if you want, classes in any other language: C#, Python, etc. You can alter or extend the default functionality, for instance, generate an HTML or Markdown report.

Out of the box, DataGrip can generate Java classes. To do this, go to the context menu of a table (or several tables) and press Scripted Extension → Generate POJO.groovy.

Choose a destination folder, and that’s it! The class-file is ready.

Generate POJO.groovy is just a script written in Groovy. It means that you can modify it and create a new script based on it, for example, for generating classes for other languages. From the same context menu, click on Go to scripts directory to see where this file is placed.

You can edit the existing one or create new scripts. Just place your new script into this folder, and it’ll be available from the context menu.

Some examples from our users:
— Improvement of default script: comment support and replacing underscores in names.
— POJO Generators for Entity
— Generator of classes for Kotlin Squash
— Export structure as markdown into the clipboard

Groovy is not the only language you can use, JavaScript is also available.

Before we also had Clojure engine and some people used it for scripting. For instance, here is the script for generating C# classes. If you strongly wish to use Clojure for scripting, please download Clojure runtime and scripting engine files here and place them in the lib folder inside the installed DataGrip folder.

We hope this post helps, feel free to ask questions if any.