DataGrip Blog

Hello, everybody! You may be keen to know what we are planning to include in this summer’s release. We’ve got a description here of what you can already try.

A new UI for boolean values

Well, this is quite a welcome development! There’s a new way to observe and edit boolean values that is more user-friendly.

Editing:
– The space key toggles values like it used to.
– Typing f, t, d, n, g, or c will input the corresponding values: false, true, default, null, generated, and computed. We’re all lucky that all these words begin with different letters!
– Typing anything else will open the drop-down with possible values.

A new UI for cropped data

Sometimes DataGrip cannot load all the data for a given cell. This happens if the size of the data in the cell is larger than allowed by the Database | Data views | Max LOB length setting. In these cases, we used to add a small piece of text, like “10 KB of 50 KB loaded”, to the value. Now instead of altering the value, we just show a hint.

Long tabs: no more!

Another usability issue that won’t annoy you in 2020.2: long tabs.

How it works now:

– The Database | General | Always show qualified names for database objects option is now turned off by default. Objects will be qualified in the tab names only if there are two objects with the same name open. For example, if you open two actor tables from different schemas, the schema name will be displayed in the tab name. Otherwise, it won’t be.

– If the data source has a name that is longer than 20 symbols, it will be truncated.

– If you have only one data source, DataGrip won’t display it in the tab name.

– If a qualified object name has more than 36 symbols, it will be cut off.

Introduce variable

This refactoring is now supported in more dialects: SQL Server, Db2, Exasol, HSQL, Redshift, and Sybase. You can introduce variables from any expression that has the simple type.

UI for creating views

While we are always advocating for people to use the Generate functionality (Alt+Ins or Cmd+N in the SQL editor) if they want to create a view, many are more comfortable using the UI. We heard you, and we’ve added a UI option for that.

Refresh database quick-fix

Sometimes you have unresolved objects in your script. When you do, DataGrip doesn’t understand where these objects are located and suspects that they don’t exist at all. While in many cases this is true, sometimes the objects are unresolved because you just need to tweak the context you are working on.

We’ve added the Refresh database quick-fix, which will help you if an object has been added to the database from somewhere else since the last time you refreshed your database.

Better filtering for MongoDB

In addition to ObjectId and ISODate, filtering now supports UUID, NumberDecimal, NumberLong, and BinData. Also, if you have a valid UUID/ObjectId/ISODate in your clipboard, you will see this value in the offered filters.

We’ve also added regular expressions to filtering, in case you are missing the LIKE filter from MongoDB.

Other improvements

– In the data editor, if you edit a one-line string value, the down/up keys will finish editing it for you.

– In the event you are experiencing network issues, introspection in Oracle databases is now faster than it was before.

– The XML extractor is now a little bit better: If the original value is already XML, the extractor will not wrap it again in the extracted XML. If the value is not already XML, then special characters ‘<‘ and ‘>’ will be converted to xml entities: &lt; and &gt;

That’s all for today! Please try our new EAP build. Your feedback is welcome in our twitter or forum.

The DataGrip team

In DataGrip 2020.1.4 for Windows there is a problem with SQL Server authentication. We are currently addressing this issue and we expect it to be resolved in 2020.1.5.

There are two workarounds to fix the problem:

Downgrade to 2020.1.3 or switch to a different version of JetBrains runtime.

Downgrading to 2020.1.3

If you use the ToolBox application, you can downgrade directly from it.

If you manually installed DataGrip, download the previous version here.

Switching to a different version of JetBrains Runtime

This workaround is more complicated but suits those who need to use the latest version of the IDE.

First, download the JetBrains Runtime from JetBrains BinTray storage. In this case, you need version 765.40 of the runtime. This is the version for Windows because the initial problems are Windows-specific.

Then install the Choose Runtime plugin in your IDE.

After that invoke Search Everywhere (press Shift twice) or Find Action (Ctrl/Cmd + Shift + A) and search for Choose Runtime. In the dialog that opens, select the runtime you’ve just downloaded.

Restart your IDE.

We hope that helps!

DataGrip team.

Introducing DataGrip 2020.1.4

DBE-10715: [PostgreSQL] Fixed a time zone error affecting PostgreSQL versions prior to 10.
DBE-7578: DataGrip no longer refreshes the database after running a query in read-only mode.
DBE-9417: Targets in the Run Configuration dialog are now filtered by dialect.

Hello! Here’s a brief overview of the important things we’ve added and fixed in 2020.1.3

Features

DBE-1845: The data editor tab appears automatically for CSV files.

DBE-9993: Pasting to the data editor automatically creates new rows.

DBE-8019: The data editor allows for scrolling beyond the last row.
DBE-10484: The file name is pre-selected in the dump data dialog.
DBE-8121: The dedicated node for trigger functions has been added to the database tree view.
DBE-10483: [MongoDB]: Collection references specified as string literals are now resolved correctly.
DBE-10410: [Redshift] Support for the syntax of materialized views has been added.

Bug-fixes

DBE-10408: No more UI freezes when editing large SQL strings.
DBE-9272: Save LOB works for the results of complex queries.

Hello! This update fixes the problem that caused extremely high CPU usage.

Hi, here is the first bug-fix update for DataGrip 2020.1.

Important bug fixes:

• DBE-10421: Using Cmd/Alt+1 to open the Database tree view also passes focus to it.
• DBE-9957: Always Select Opened Element in the Services tool window can be disabled.
• DBE-10383: Parts of cells from in-editor results can be copied.

Hi,

In the run-up to the 2020.1 release, which is scheduled for next week, here is a Release Candidate.

What’s new in this RC

The Import file action is now available:

– In the context menu of the CSV file, and
– In the context menu of the editor when a CSV file is opened.

The text data viewer uses the color of the data source.

The tab name becomes the file name when exporting data.

Your DataGrip team

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