DataGrip 2019.3 EAP 3

Maksim Sobolevskiy

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.

TreeView

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.

Progress

Flame chart for explain plan

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

FG1

Here’s how it looks:

FG2

New inspections and warnings

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

InspNullColumn

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

InspCoalesce

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

InspOffset

That’s all, folks!

The DataGrip Team

Comments below can no longer be edited.

8 Responses to DataGrip 2019.3 EAP 3

  1. MTS says:

    November 8, 2019

    i can not see the inline query progress when running a sql statement. Is there a setting i need to turn on?

    • Maksim Sobolevskiy says:

      November 12, 2019

      But your query is rather long for this progress, right? What database do you use?

      • MTS says:

        November 12, 2019

        sql server, statement i am running is around a min

        • Maksim Sobolevskiy says:

          November 18, 2019

          Still the same with the latest EAP?

  2. MTS says:

    November 8, 2019

    how can you see Inline query progress? It doesn’t show when i run sql queries. Setting?

  3. S says:

    November 11, 2019

    I think this update broke the “Always Select Opened Element” option, it’s stuck on.

  4. Peter Gannushkin says:

    December 13, 2019

    I appreciate the effort with analyzing COALESCE, however, it gets confused if the query has a LEFT JOIN. Consider the example below. Since I’m doing a LEFT JOIN it is possible that t.name is NULL, therefore redundant code warning is misleading and incorrect.

    CREATE TABLE one (id INT);
    CREATE TABLE two (id INT, name VARCHAR(10) NOT NULL);

    SELECT COALESCE(t.name, ‘default value’)
    FROM one o
    LEFT JOIN two t ON t.id = o.id

    Thanks!

    • Maksim Sobolevskiy says:

      December 23, 2019

      Thanks, we’ve just fixed it! expect in the closest update.