Hi!

All IntelliJ-based IDEs are nearing the 2018.3 release, and today we’ve got a DataGrip 2018.3 RC. Let’s have a look at what’s been added since the latest EAP.

Previously, each new query console meant a new connection. In the new version, it’s possible to work with just one connection for the data source and have all consoles use that same one connection. This allows you to see the temporary objects in the database tree, or use the same transaction in different consoles. This is our first step toward creating full connection management in DataGrip.

To turn it on, go to Data source properties -> Options -> Single connection mode.

We’ve also added the ability to define colors for data sources to the Properties dialog.

Another small improvement is a new inspection called Unreachable code.

That’s about it! Your feedback is welcome, as always, in Twitter, the forum, and the issue tracker. Let us know what you think about this new release!

Your DataGrip Team

DataGrip 2018.3 EAP 4

The next build for DataGrip 2018.3 is here.

There is a new setting: automatically add aliases when completing table names. But, if the aliases we generated don’t really suit you, create your own for particular tables.

Here’s the example:

There are a lot of fixes around the Extract subquery as a CTE action. For those of you who don’t know about it: it’s placed under Refactor -> Extract -> Subquery as CTE. But we think it’s easier to use Find Action. Or assign a shortcut!

– The name suggested for CTE doesn’t bring conflicts: DBE-6496
– Context is properly defined if a statement is wrapped in another expression (DBE-6503, DBE-6517)
– DataGrip won’t suggest extracting CTE when the column aliases in an as-expression for dialects that don’t support it (DBE-6490)
– This refactoring is enabled for MySQL: CTEs are supported since MySQL 8

And a small fix for INSERT live template: now the column names hint appears automatically: there is no longer any need to press Ctrl/Cmd+P!

That’s it! Your feedback is welcome in Twitter, the forum, and the issue tracker. Let us know what you think about our new release!

The DataGrip Team

DataGrip 2018.3 EAP 3

The next build for DataGrip 2018.3 is here.

We continue polishing Cassandra support. In this release the Modify Table UI became clearer, and also we’ve fixed the bug with casing: now you can manage objects with capital letters in their names.

Our team will highly appreciate it if you try out our EAP builds with Cassandra.

What else is here?

One of the most important SQL refactorings is finally here: introduce alias. Take your stop-watch and count how much time it’ll save!

We’ve added the new setting called Invert order of operands in auto-generated ON clause:

If it’s off, the FROM table will be the first in JOIN condition.

If it’s on, vice versa:

A new inspection was added: Unused subquery item. It’ll help make your code neater.

That’s it! Your feedback is welcome in Twitter, forum, and issue tracker. Let us know what you think about our new release!

DataGrip team

DataGrip 2018.3 EAP

Hello! The next build for DataGrip 2018.3 is here. Let’s see what’s inside.

Cassandra database

We’re gradually finding our feet with NoSQL. After adding Clickhouse support in 2018.2.2, we have now gone on to add the support for Cassandra.

Please, try it out and share your feedback with us! This time right now, before the release is set in stone, is the best time to let us know what you think as improvements can still be made on the fly.

Generating files from objects

Now, if you use the SQL Generator (Ctrl/Cmd+Alt+G) for getting the DDL from objects, you can also generate the SQL files for these objects. To do this press the save button on the left pane.

As you can see, we’ve created two layouts for the output. The UI is not quite finished yet, so please, if you have any ideas you would like implemented share them with us: what kind of settings you would like to see here.

Anyway, now you can press Edit button to the right of the Layout drop-down and edit any of them. Or create your own. These layouts are just groovy scripts.

Better foldings

Enhancements in this area:
— Single lines cannot be folded.
— Text for foldings now has more information.
— Expression/declaration lists can be folded:

Completion for window functions

Now DataGrip automatically adds OVER() and puts the caret into the appropriate place

Drop cascade

We’ve added a ‘Use drop cascade syntax’ option when dropping an object from the database tree.

Page size

We’ve also reworked the UI for the page size a bit. Now it’s clear how to see all the rows from a table or a result.

That’s it! Your feedback is welcome in our Twitter, forum, and issue tracker. Let us know what you think about our new release!

DataGrip team

DataGrip 2018.3 EAP

Hello! No long preambles, this is DataGrip 2018.3 EAP! Let’s see what’s inside.

Code completion

Many feature requests are implemented in this area.

When you use the GROUP BY statement, DataGrip offers you a list of non-aggregated fields.

A list of all columns is available in completion after the SELECT keyword.

We also added this list to the MERGE statement and now it works with INSERT INTO when using table variables.

Completion now works well for named parameters.

In the case of ambiguous names, DataGrip now shows you the context.

We also introduced Postfix completion which might be familiar for those who use other IntelliJ-based IDEs.

Here is a movie of how all of them work.

Code completion also works for:

— Items in brackets. DBE-4246
— Numeric fields in SUM() and AVG () functions. DBE-2285
— FILTER (WHERE …) clause of an aggregate function.DBE-5591
— Table value types.DBE-5768
— Field types in SQLite. DBE-5660, DBE-6778

Now there is an ability to choose a dialect for Live Templates. It means that this live template will only work in the specified dialect.

This ability lets you create different dialect-based implementations for the same abbreviation. Say, we want to create a template for getting the first n rows. In SQL Server and PostgreSQL, this query would have different syntax.

One can use the same abbreviations for different live templates if they are in different groups. Create two new groups: SQL Server and PostgreSQL. In each group create a corresponding live template with the appropriate syntax.

Don’t forget to choose the right dialect for templates. Thus, they will work only in the needed context.

Another small improvement: the Create table intention (did you know about that?) now respects field types and generates the correct code. Press Alt+Enter if there is a table where you are going to insert data.

The result is:

Code insight

Now DataGrip will warn you if you use the DELETE or UPDATE statement without WHERE clause.

In case you are running this, there will be a caution notice.

Other enhancements

We support extensions in PostgreSQL.

Quick doc for the data source (Ctrl+Q for Windows/Linux, F1 for OSX) now contains some statistics: the number of different objects

Also, the long-awaited auto-reconnect feature is added: no more disonnections after timeouts!

Fixes

Support for:
— Stored procedures in PostgreSQL 11. DBE-6863
— ROWS FROM in PostgreSQL. DBE-7098
— Vector valued updates in SQLite. DBE-4449
Other:
— If JOIN has no condition, this error is highlighted. DBE-6759
— ‘@’symbol doesn’t break the spell checker, thus it works in variables’ names. DBE-2250
— JSON groovy extractor works OK with big numbers. DBE-7019
— Row count works if columns are sorted. DBE-2444
— Сorrect search path is set in the reopened data editor. DBE-7044
— Query plan visualiser works in Redshift. DBE-7129

That’s all for today. Your feedback is welcome in our twitter or forum. By the way, starting from this version, we have a handy thing: click Help -> Report problem… to create a new issue in our issue tracker.

DataGrip team.

Hello! This is another minor update for 2018.2. It includes several important bug-fixes.

Some people complained that the new SQL log was not really very friendly: the output panel would become hard to read due to the number of internal queries. So, we removed the internal queries from this panel: now you will see only the queries which were run explicitly by the user, including those, which were run from the UI.

If you still need to inspect literally all the queries that DataGrip has run, check the SQL log file: Help → Show SQL log.

Other fixes:

DBE-6889: DataGrip executes procedures fine with old MySQL jdbc connectors.
DBE-6982: No more deadlock in read-only mode.
DBE-6810: We fixed the highlighting in DB2.
DBE-5459: Internal files are not shown in the Go to File list.
DBE-6939: No more lags in code formatter settings preview.
DBE-6823: Custom code style can be used as default.

Hello! This is a first small update for 2018.2 Here is the list of important enhancements:

Owners are generated in PostgreSQL and Redshift

New experimental Search Everywhere

IntelliJ Platform 2018.3 will introduce some changes that you can already start playing with, namely a new Search Everywhere dialog. It is the result of merging Search Everywhere, Go to table/procedure/class, Go to file, Go to symbol, and Find action.

To turn it on, open the Maintenance dialog (Ctrl+Alt+Shift+/ on Windows and Linux or Cmd+Alt+Shift+/ on macOS), select Experimental features, and enable the new.search.everywhere check-box. Please keep in mind that this feature is still under heavy development.

Bug fixes

DBE-6751: Default precision for common data types are now generated when executing a procedure.
DBE-6818: Working with Postgres 11 is possible now.
DBE-6753: Drag and drop works to move data source to a group.
DBE-6796: Data source group name can be used when navigation to an object.
DBE-6797: Slashes work as a path separator when renaming a data source.