DataGrip 2020.1 EAP 4

Hello! Here are some improvements from the next build for the DataGrip 2020.1 EAP

CSV file type

DataGrip now has a registered *.csv file type. This means that you will no longer get a notification about CSV supporting available plugins. DataGrip also has the ability to edit CSV files as tables. You will see a floating toolbar with the Edit as Table button.


If you click this button and define the CSV format in the corresponding dialog, then the editable table with the content of your CSV file will open. Two tabs for the file become visible: Text and Data.


Easy navigation to Execute settings

If your file contains several queries, when you run one of them you’ll see the chooser.

Some people love this chooser, but some don’t. We’ve made it easier to customize the behavior of the Execute action.


The customize link pictured above will lead you to Settings/Preferences, where you can define whether you want to see the chooser or always run the statement under the caret. You can also choose another type of behavior.


Stay tuned for more updates!

The DataGrip team

Posted in Uncategorized | 2 Comments

DataGrip 2020.1 EAP 3

Hello! Here’s our next build for DataGrip 2020.1 EAP.

Better coding assistance for MongoDB

Now you have:

– Resolve and completion of collection names.
– Completion of methods.


Better exporting

In this release cycle, we have focused on making exporting more user-friendly.

First, we’ve cleaned up the menu:


Second, we’ve created a dialog window for exporting:


Mark as plain text

If you need to edit a really huge script, now you can mark it as plain text and open it for editing. Highlighting and coding assistance will be off, so you can modify it with no performance lags.


Stay tuned for more updates!

The DataGrip Team

Posted in Uncategorized | 3 Comments

DataGrip 2019.3.4


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

Better subquery folding

Based on DBE-10131, we’ve added a new option for subquery folding:


Important bug-fixes

– DBE-9436 [Redshift] Synchronizing works with the latest JDBC driver. It can cause significant performance issues, however, so if you experience any, please report them.
– DBE-9654: [SQL Server] Import data works correctly with auto_increment columns.
– DBE-10189: Wildcard is used for Preview update when the table is unresolved.
– DBE-10125: Fixed the false positive in the Unused expression inspection.
– DBE-9988, DBE-10134: Fixed the false positive in the Redundant COALESCE inspection.


The DataGrip Team

Posted in Uncategorized | Leave a comment

DataGrip 2020.1 EAP 2

Hello! Here’s yet another build in our EAP for DataGrip 2020.1.

Export to Excel



Text data viewer

Now you can choose your preferred data format in the extractor drop-down.


In-editor results

We keep polishing one of the brightest features of this release. The big challenge has been to make scrolling user-friendly. Now DataGrip can detect whether you are scrolling the data or the code editor itself.


Attach directory

The File | Open menu now attaches the directory to the project.


Just to be clear, the attached directory is the directory you see in the Files tool window.

utPLSQL support

– utPLSQL support is now compatible with DataGrip versions earlier than 3.6.
– We’ve added Run by tag functionality.

Bug fixes

DBE-8365: [Redshift] Syntax for stored procedures is supported.
DBE-9436: [Redshift] Synchronizing works with the latest JDBC driver. It can cause significant performance issues, please, report if there are any.

Posted in Uncategorized | 1 Comment

We open EAP for DataGrip 2020.1

Hello! It’s time to start our EAP for 2020.1. As usual, you don’t need to have a subscription to use them, and regardless of whether you have a subscription or not, we would still truly appreciate your participation. Your feedback will help us ensure that what we release this April is of the highest quality!

So, let’s take a look at what’s featured in the EAP!

Run configurations

This concept is already in use in our other IDEs, and it’s now come to DataGrip. In general, if you want to run something, you just need to create a configuration for it. Let’s look at how this can help you with particular tasks.

Configuration for running script files

Before, you could only run files one by one. This could be especially frustrating if the files included dependencies and the order was crucial. Now, you can run several files at once.


Choosing to run multiple files creates the run configuration. In this configuration, you can reorder the files, add new ones, and run other programs or configurations before launch.


Your run configuration will be saved automatically. If you want to run this configuration several times but you only want to change the target, tick the Show this page checkbox, which will offer you the option to change the target and other options every time you run the configuration.

Configuration for running code

You can also create a configuration that will run the saved code snippet.


Saved run configurations can be found either on the Navigation bar or in the Run menu.


There you will see the list of all configurations you have.

Screenshot 2020-02-27 13.44.45

Test frameworks support

utPLSQL is a popular framework for testing PL/SQL code in an Oracle database. We’ve built support for it, which means that you can now run tests and test packages without having to leave the code editor. Just click the small green play button on the left-hand pane.


A temporary configuration is created with each run. It will be deleted after some time, but you can create a permanent configuration in the utPLSQL section.


Tsqlt, the test framework for SQL Server, is also getting support in DataGrip 2020.1. To run one ot multiple tests from the database explorer, press Ctrl/Cmd+Shit+F10.


Results in editor

Now you can see the results in the code editor. We hope this will fit nicely into the flow of many of our users, which is why we even went so far as to turn it on for everybody!


We do understand that not everyone wants to change their habits, so there’s a setting to turn it off for the whole IDE: Settings/Preferences | Database | General | Show output results in the editor.

There is also a button on the toolbar which toggles two of the possible modes.

Geo viewer

This feature is DataGrip-only.

To get the view of geographical data in the data editor, click the Gear icon and then select Show Geo Viewer.


The geo data viewer works only if JCEF is enabled.

In rare cases, enabling JCEF might crash the IDE. It can happen if you have installed plugins that use JavaFX. Here are the instructions for recovering your IDE in the unlikely event this crash happens to you:

1. Locate the config folder of your IDE (for help see

2. Locate the file <config folder>/options/ide.general.xml

3. Remove the following line from ide.general.xml:

<entry key="ide.browser.jcef.enabled" value="true" />

If you run into any difficulties, please contact us at

Context data sources scope

In DataGrip 2020.1, it’s possible to search for an object in the context data source, that is, the data source you are working with at the moment. The context can be defined either from the console you are working with, the data editor or by selecting it in the database explorer.

If you select several data sources, the search will be performed in all of them.



New authentication options

We’ve added support for pg_pass in PostgreSQL:


We’ve also added the ability to use the domain credentials for the SQL Server if you’re using the jTds driver. Before, this was way more complicated and required a lot of configuration in the Advanced tab. That’s no longer the case!


Shared SSH configuration

Now you can create a configuration of the SSH tunnel and use it in many data sources or even projects.


Update preview

There is a new intention action for the UPDATE statement. Now, DataGrip will simply run a SELECT statement with the same WHERE clause.

To run it, first press Alt+Enter on the UPDATE statement and then choose Preview update.


And voila! DataGrip will add columns with the new values next to the old ones.


Datetime injection

Now, if you use DATE before a string literal to convert it, DataGrip understands that this string contains a date and highlights it accordingly. The IDE also warns you if something is wrong with this data.


At the moment, this feature only works with this type of conversion for MySQL, Oracle, DB2, and H2.

Filtering data in MongoDB

We’ve added support for filtering in the data editor for MongoDB.


That’s all for today. We welcome your feedback either in our forum or on twitter. You can also use Help | Report problem… to create a new issue in our issue tracker.

Thanks for your support!

Your DataGrip Team

Posted in Uncategorized | 1 Comment

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 , | 9 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