DataGrip 2018.1 EAP 2

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.

Posted in Uncategorized | Leave a comment

DataGrip 2017.3.7

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
The Drive to Develop

Posted in Uncategorized | Leave a comment

DataGrip 2017.3.6

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
The Drive to Develop

Posted in Uncategorized | Leave a comment

We open EAP for DataGrip 2018.1

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.


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

Posted in Uncategorized | 10 Comments

DataGrip 2017.3.5

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

Posted in Uncategorized | Leave a comment

Generate simple classes from database objects in DataGrip


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.

Posted in Uncategorized | 5 Comments

DataGrip 2017.3.4

Here is the first bug-fix update this year. Many issues have been fixed, the most important of which are:

Collations are now placed after schemas in the database tree. If you want to hide them, put collation:-.*  into Data source properties → Options tab → Object filter.


DBE-5703: А correct DDL statement is now generated when a PostgreSQL function with defaults is dropped.
DBE-5608: Amazon Redshift data source synchronization works now.
DBE-5404: The editor now recognizes the WITH NO SCHEMA BINDING syntax in Redshift.
DBE-2465FETCH ALL IN <cursor name> doesn’t return errors anymore.
DBE-5274: FOR EACH ROW WHEN in triggers shows the correct clause.
DBE-4983: SQL generator doesn’t add the ‘n’ character in new lines in Oracle anymore.

Fixed freezes:
DBE-2536: While introspecting schemas with many tables.
DBE-5532: After updating a function.

DataGrip team

Posted in Uncategorized | 15 Comments

DataGrip 2017.3.3

This update brings an important fix of  “Out of memory” problem: IDEA-183889

Posted in Uncategorized | 3 Comments

DataGrip 2017.3.2

Hello! This is another minor update for 2017.3. It brings several important bug-fixes:

DBE-5031 – Enum fields are now available for editing. Completion is not yet implemented.
DBE-5512 – Fixed bug with saving LOBs.
DBE-4426 – DataGrip now can connect to FrontBase. There are still some known issues with transactions.

DataGrip team

Posted in Uncategorized | 15 Comments

DataGrip 2017.3.1

Only a week has passed since we released DataGrip 2017.3, and we are already delivering you the first minor update. Among various bug-fixes there is something new to try!

IDE-level read-only mode

For ages DataGrip had a Read-Only mode that could be turned on in the data source properties.


It just turned on read-only mode in the corresponding jdbc-driver. This denied running modification queries in MySQL, PostgreSQL, AWS Redshift, H2 and Derby. In other DBMS’s it did nothing.
In DataGrip 2017.3.1 we have added an IDE-level read-only mode. Now it is activated along with the jdbc-level one, the check-box turns on both. Thus, in read-only mode every DDL or DML query will be underlined.


If you execute it, there will be a warning.


Anyway, it is possible to press Execute on this bar if you’re totally confident in what you are doing.

We also now index the source codes of functions and procedures, and build a call-tree behind. It means that if a function executes another function (repeat n times) which executes DDL or DML statements, you’ll also see the warning.

That’s it. Please, report to us if you have any need for two independent check-boxes for jdbc-level and IDE-level read-only modes.

Background images

If you set a background image via Preferences/Settings → Appearance → Background images, now there are new alignment options: center image, stretch image or make a texture. The very right square lets you to choose the anchor.


Snap packages

DataGrip is now also available as a snap package. If you’re on Ubuntu 16.04 or later, you can install DataGrip from the command line:

sudo snap install datagrip --classic

Thank you for reading this, we hope you got a lot out of it!
Your DataGrip Team
The Drive to Develop

Posted in Uncategorized | Leave a comment