DataGrip 2019.3.3


Here is the third bug-fix update for DataGrip 2019.3.

Important bug-fixes

  • The right schema is used when adding a foreign key constraint to a table. DBE-9743
  • Auto sync is working after a DROP followed by a CREATE statement. DBE-9980
  • No more freezes in JOIN completion. DBE-9844
  • [Oracle] The OracleSqlPlus dialect is back. DBE-10030
  • [ClickHouse] Deleting rows works as expected.
  • [BigQuery] Identifiers are quoted using back quotes.
  • [BigQuery] LIMIT and OFFSET are generated when opening a table’s data.


The DataGrip Team

Posted in Uncategorized | 4 Comments

DataGrip 2019.3.2: Virtual foreign keys and more!

Hello! This is the second bugfix update for DataGrip 2019.3. Here’s what it has inside:

Virtual foreign keys

We’ve introduced the concept of virtual foreign keys. You can use this concept in the event that you need to use a relationship that exists but is not located in your database.!

Doing so will help you:
– Have the proper completion when writing JOIN clauses.
– See the relations in diagrams.

By default, DataGrip tries to guess if you have relations between columns whose names contain id. It looks like this:


These relations are also displayed in the diagram. If you don’t want them to be there, just click on the corresponding icon on the toolbar.


You can also create a custom rule under Settings | Preferences for guessing whether there are relations: :


As you can see, DataGrip 2019.3 only includes one pre-built pattern, which was particularly designed to handle the examples above. You can add your own with the help of the regular expressions. To learn more about this feature, you can visit our help page.

When you write code, any relation from the JOIN clause can be stored as a virtual foreign key. Press Alt+Enter and choose Store table relation.


DataGrip will ask you to identify a file where these virtual relations will be stored.


The resulting XML file will look like this, and you can then edit it directly:


Stored procedure runner for MySQL

Finally, after adding the option to execute stored procedures in PostgreSQL, MS SQL and Oracle, we’ve now made it possible to do so in MySQL.


Important bug-fixes

DBE-9829 Aliases are no longer used when completing table names in DDL.
DBE-9800 Only trigger functions are offered in the corresponding completion list.
DBE-9803 The wildcard is now resolved inside row constructors.


DataGrip team.

Posted in Uncategorized | 4 Comments

DataGrip 2019.3.1

Hello! This is the first bugfix update for DataGrip 2019.3. Here’s what it has inside:

  • DBE-9708: A new option lets you choose whether you want to use schema qualifications when using JOIN.

Screenshot 2019-12-19 15.25.39

  • DBE-9736: The table filter is cleared when opening a table from the database explorer.
  • DBE-9743: The correct schema is used when adding a foreign key.
  • DBE-9728: Fixed the bug with queries seeping into column names.
  • DBE-9714: Right-clicking on a column header shows the menu again.
  • DBE-8196: A new registry option to remove the schema qualification when updating data.
Posted in Uncategorized | Leave a comment

DataGrip 2019.3: MongoDB support, Debugger for Oracle, Inline query progress and more!

We’re pleased to introduce DataGrip 2019.3. This is the third major update of 2019, and it’s packed with various enhancements. Let’s take a look at what it has to offer!


MongoDB support

The day has finally come for us to start adding MongoDB support. Since the request received more than 400 votes, we decided that the time was ripe to begin including basic functionality for it.


Here’s a quick overview of the MongoDB features that work in this version:

Introspection: You can observe collections and fields in the database explorer.

Data viewer: Open any collection or observe the query result and you have the option to sort it by column or filter the values. Paging works, as well.

Tree view: It’s also possible to explore a tree view of the data. To turn it on, click the Gear icon | View as… | Tree.

Query console: To run a statement, put the caret on it and run the console by pressing Ctrl/Cmd+Enter, or use the Play button on the toolbar.

Oracle PL/SQL debugger

In this first version of the long-awaited PL/SQL debugger, you can debug procedures, functions, triggers, and anonymous blocks, and observe variables.


You can visit our help page to learn more about how the debugger works. If you have any feedback for us about the debugger, please don’t hesitate to post it in the corresponding issue.

Working with the source code

  • Diff viewer for routines
  • 3-way merge
  • Code prettifier in PostgreSQL
  • Intentions now work inside the source codes


Running queries

  • Inline query progress
  • Flame chart for explain plan


Coding assistance

  • New inspections
  • New intention actions
  • An option to sort lines alphabetically
  • An option to search only in a selected area
  • Resolve respects filtering
  • New items in the Generate menu


Data editor

  • There are no longer problems with ambiguous names in the result-set.
  • The Modify Table action is now available from the data editor context.


To take in all the new features with full descriptions, please visit the What’s New page.
You already know all of this, but just as a quick reminder:

Thank you for your attention!
Your DataGrip Team

Posted in Features, Releases | Tagged , | 10 Comments

DataGrip 2019.3 EAP 4

Hello, today we have a new build for the DataGrip 2019.3 EAP for you to try.

DBE-7976: The Modify Table action is now available from the data editor context. Want to add a new column while editing table data? Just press Ctr/Cmd+F6 and go ahead!

Screenshot 2019-11-15 00.51.31

DBE-9336: Intentions now work inside the source code of routines. For example, if you want to expand the wildcard via Alt+Enter on an asterisk, now this is possible.

Screenshot 2019-11-15 00.46.53

DBE-9548: Now if your result-set contains multiple columns with the same name, you won’t have any problems with ambiguous names if you create a table from it.

Screenshot 2019-11-15 00.50.41

DBE-9428: A new intention is introduced to help you convert JOIN ON to JOIN USING, and vice versa.

Screenshot 2019-11-15 00.47.14

That’s all, folks!

The DataGrip Team

Posted in Uncategorized | Leave a comment

DataGrip 2019.3 EAP 3

Hello! It’s time for a new EAP build for 2019.3 which is due for release this December.

Tree data view

We’re continuing to build on the MongoDB support. We’ve just crossed another milestone with this process by adding the tree data view.


To turn it on, click the Gear icon -> View as… -> Tree.

Inline query progress

Now you can clearly see when your query is running: there is a spinning icon on the gutter and the inline live timer as well.


Flame chart for explain plan

We’ve added a new type of visualization for the explain
results. To see it, click the corresponding button on the right. It is just under the
diagram button.


Here’s how it looks:


New inspections and warnings

If you try to paste null into a not nullable column, you will get:


If the first argument in your COALESCE call is not nullable, you will get:


If you use TOP and OFFSET simultaneously in SQL Server, you will get:


That’s all, folks!

The DataGrip Team

Posted in Uncategorized | 8 Comments

DataGrip 2019.2.6

DataGrip 2019.2.6 is Out!

– Result tabs switch with the consoles again.
– No more freezes on MacOS Catalina when exporting data. DBE-9334 
– Fixed the bugs with the external tables in Redshift not showing. DBE-9181 
– Various bugs with paging are fixed. DBE-9217 
– Column names are no longer collapsed when the data editor is transposed. DBE-8904 
– The “column specified more than once” error does not appear for data import anymore. DBE-9283 
– The table and column comments are not truncated anymore. DBE-8000 
– There are no longer false warnings about the number of values when selecting the identity column. DBE-8924 

Posted in Uncategorized | Leave a comment

DataGrip 2019.3 EAP 2

Hello! It’s time for the new EAP build for 2019.3 that is going to be released this December. Let’s take a look at several new features.

Oracle PL/SQL debugger

We’ve started working on a debugger for Oracle PL/SQL. Right now, it provides just basic functionality: you can debug procedures, functions, triggers, anonymous blocks and observe variables there.

Updates to this feature and additional information will appear in the corresponding issue.


Search with Google for connection error

It’s now easier to deal with connection errors! When a connection fails, it’s possible to Google the error text using the corresponding button.


Drop action keyboard shortcut remapping

We’ve updated the Drop action and made it available for shortcut remapping. Before, it used the shortcut of the Delete action. If you don’t want to have the default shortcut for the Drop action, it’s now possible to remap it from the settings.


That’s it!

The DataGrip team.

Posted in Uncategorized | 5 Comments

DataGrip 2019.3 EAP is Open!

Hello! We have begun our DataGrip 2019.3 EAP and there is something really exciting inside.

MongoDB support

Finally, the day has come for us to start working on MongoDB support. After more than 400 votes we have decided now is a good time to begin including at least some very basic functionality.

What actually works now:


You can observe collections and fields in the database explorer. We fetch the first 10 documents from each collection to get information about the fields. This can be customized via the JDBC parameter fetch_documents_for_metainfo which is available in the Advanced tab of the data source properties dialog.


Data viewer

Open any collection or observe the query result and you can sort by columns or filter the values also paging works as well.


Query console

There is currently no coding assistance, but this doesn’t stop you running queries and getting the results. To run a statement, select it and run it via Ctr/Cmd+Enter or by using the Play button on the toolbar.


These commands are available right now:

use <database>
show databases or show dbs
show collections
db.collection.update({…}, {…})
db.collection.updateOne({…}, {…})

The EAP program stage is the best time to provide your feedback, so please comment here or create issues in our tracker.

3-way source code merge

When you submit source code and DataGrip determines that it was changed while you were editing it, a notification will pop up. This notification will suggest you to resolve the conflict by way of a three-way-merge.


Also, don’t forget that if you want to make sure that you won’t be deleting someone else’s work by submitting an outdated object, the Warn if editing outdated DDL option should be turned on.


That’s it!

DataGrip team.

Posted in EAP | 9 Comments

DataGrip 2019.2.5

Hi! We have an update for 2019.2. Some bug-fixes are inside.

– Improvements in H2 grammar support.
DBE-7893 [PostgreSQL] Procedure is back to the Generate menu.
DBE-9098 Fixed the bug with importing data from CSV files that include an IDENTITY column.
DBE-9105 Numbers at the beginning of table names are supported again.
DBE-9093 The Replace IN intention doesn’t corrupt code anymore.

Posted in Uncategorized | 3 Comments