Early Access Program Features News

DataGrip 2019.1 EAP 2

We have a new build for the 2019.1 EAP available. The major release of DataGrip 2019.1 is planned for early April.


We’ve completely reworked the connection dialog. Some changes are only related to the UI, but there are some new features as well.


We’ve re-arranged the fields here to make the connection process more user-friendly.

Comparing to the previous EAP build, password saving is now implemented via a drop-down. Now it has three options: Never, Until restart, and Forever. We are still thinking of adding some more options. Also, the empty password now can be set via UI: use the context menu.


The Connection type field is what before was URL type. It determines the whole UI of this dialog, which is why now it’s on top along with the driver chooser.

The Database field goes after the credentials because sometimes credentials are needed to provide the database list. The list should be invoked by Ctrl/Cmd+Space.



Read-only, Auto-Sync and Transaction control settings have been transferred here from the General tab.

Newly introduced settings:

Run keep-alive query every N seconds will help you keep the connection alive. You can define the custom query in the driver settings for unsupported databases.
Auto-disconnect after N seconds. Pretty self-explanatory.
The startup script is an SQL query which will be run each time you establish a connection. Remember that if the Single connection mode is unchecked, each new console creates a new connection.


Renamed setting:

Warn if editing an outdated DDL is the new name for Notify when the outdated object is opened.


– Object filter is transferred here from the Options tab.


There’s a new Recent Locations popup that lists you recently visited/changed code locations. It presents them as code snippets with a couple of lines before and after the location.

This popup was inspired by Recent Files, but with an ability to search by visited code locations. This should come in handy when you remember what the code was about but can’t recall where it’s located. Especially if you work with several query consoles: they usually have similar names!


Press Delete/Backspace to remove locations from the popup.

The default shortcut for this popup is Ctrl/Cmd+Shift+E. If you’re used to pressing Ctrl/Cmd+Shift+E to call up Recently changed files, please use double Ctrl+E for that instead.


Support for databases

We’ve implemented introspection and code generation for Greenplum. Even partitions, an important type of objects in Greenplum, are shown in the database tree view.


DB2 now shows triggers in the database tree view.


Bug fixes:

DBE-2114: No more wrong COUNT() results in SQL Server. The driver problem isn’t fixed yet, so we’ve made changes on our side.
DBE-7743: Fixed error during introspection in MariaDB.

That’s all for today. Your feedback is extremely welcome in our twitter or forum.

Click Help -> Report problem… to raise a new issue in our issue tracker.

The DataGrip Team

Comments below can no longer be edited.

4 Responses to DataGrip 2019.1 EAP 2

  1. Avatar

    Juraj says:

    March 21, 2019

    I’m using Greenplum 5.7.0, which is a bit older version. Currently I’m experiencing following error with PostgreSQL drivers:
    ERROR: argument to pg_get_expr() must come from system catalogs

    I assume this is a problem that have been already resolved in later version, may I know what version are you using for your testing ? According picture it looks like 5.8 and 4. I would like to test this and eliminate user error.

    Thank you

    • Avatar

      Maksim Sobolevskiy says:

      March 21, 2019

      Do you have this error with Greenplum driver?

      • Avatar

        Juraj says:

        March 22, 2019

        No, but I think that’s due to fact it is using generic ODBC introspection with GreemPlum driver. I have also tested this with postgres drivers on 4.3, 5.8 and 5.17 using datagrip dockerfiles and it was working fine, unfortunately I was unable to test it on different 5.7 database as PPA doesn’t hold older versions.

        But I still believe this was likely fixed later version (10.2?), so I can update you once we have done upgrade on our corporate side ( but it may take few months ). For now I can use JDBC metadata introspection.

        • Avatar

          Juraj says:

          March 22, 2019

          I have managed to replicate this on 5.8 and 5.17.

          Problem seems to be with privileges.
          I have tried to create following user:

          CREATE USER tester1 WITH PASSWORD ‘tester1’;
          GRANT USAGE ON SCHEMA public TO tester1;

          And I did get same error with above user.
          However once I altered it to superuser with:

          ALTER USER tester1 WITH SUPERUSER;

          It was working good.

          I found issue on GitHub referencing same/similar problem tagged for 6.0.0 Beta1:
          But I could not replicate same error with query by poster, and I even tried to grant all privileges to user and only thing that made difference is superuser right.

          GRANT ALL PRIVILEGES ON DATABASE testdb to tester1;

          Hope this helps someone.