DataGrip and GitHub: Step-by-step Integration

All the IDEs based on IntelliJ Platform have Version Control System integration. DataGrip is no exception! But because database developers usually do things a little differently to other developers and because DataGrip’s project model has its own specific workflow, the integration between the IDE and VCS support isn’t quite as straightforward as with other JetBrains IDEs.


We’ll cover two general use cases:

— Cloning an existing GitHub repository with SQL scripts and other files

— Sharing a user scripts directory on GitHub

In DataGrip, VCS support doesn’t come out of the box. To have support for a particular version control system, please install the corresponding JetBrains plugin from Settings → Plugins. Since we’re going to work with GitHub, we’ll need the Git Integration plugin and the GitHub plugin.

They’re both provided by JetBrains which is indicated by the small JB icon on them. Note that they can appear at the end of the list. This happens because we use a special plugin repository in DataGrip.

Once you’ve installed these two plugins and restarted DataGrip, please go to Settings | Version Control | GitHub. Add your GitHub account there so the IDE is able to connect and use it during interactions with GitHub.

The GitHub plugin is a must if you use two-factor authentication. If everything is OK, you’ll see that your account is linked.

Your IDE is ready to work with GitHub. Let’s go through the use cases we mentioned above.

Cloning an existing GitHub repository with SQL-scripts and other files

Say you want to work with an existing GitHub repository. To clone it go to VCS | Git | Clone…
We should mention that all the actions, including this one, can be performed from any place in the IDE via Find Action (Ctrl/Cmd + Shift + A). Anyway, there is a way to do this through the menu too – see our screenshot.

Paste the link to the GitHub repository in the URL field and click Test. Hopefully, everything goes smoothly. In our example, we will clone the public DataGrip repository with various database dumps:

DataGrip will ask you a question:
— Would you like to open this directory?
— No

By clicking No, you indicate that you want to work with the repository from an existing project where you have already attached directories and have connections.

If you click Yes, it will suggest that you create a new project.

So, now you’re still in your project. The connections are in the left part, but the directory mapped to the GitHub repository isn’t attached and you don’t see it in the Files tool window. So, you need to attach it!

— Open Files tool window (Alt/Cmd+2).
— Invoke the context menu.
— Click Attach directory.


The only thing left to do is to register root. To do that, go to Settings | Version Control, locate the folder that is needed, and click +.

Now you’re ready to change your files, commit, and push your changes!


Sharing the user scripts directory on GitHub

Perhaps you’ve realized that you can’t track changes on your SQL files and you cannot revert to previous versions of your scripts. In some cases, the Local History is the only thing you need, but sharing scripts on GitHub can also be a good idea.

When you work with files in DataGrip, you need to attach the directory from your computer to the Files tool window. If you have no folders attached yet, you can do it from the context menu.

If you have already and worked with it – great! Say we have a MyScripts folder which we want to share on GitHub. First, we need to create a Git repository on our machine which will then will be linked with the remote one on GitHub.

Go to VCS | Import into Version Control | Create Git repository.

Choose the folder. In my case, it is the folder MyScripts.

The local repository is created. Now let’s create an empty remote repository on GitHub. Log in to your account and click + | New repository.

Define all the fields you need and click Create repository. That’s it! Done!

If you used the option Initialize this repository with a README, don’t forget to pull your repository before pushing commits.

The final thing we need to do is to add this remote repository to our local one. Go to Git | Remotes…


Choose the repository you need and click +.


Paste the repository address in the URL field and click OK.


Now you can commit and push your files.


The first push will actually create all the files that you need in the remote repository.

After performing Push, we have all the files we need on GitHub!

That’s it! One last thing to mention:

You can tell DataGrip which SQL dialect is used in the work directories so that the IDE can analyze your code correctly. To define dialects for the directories, go to Settings | SQL Dialects.


If you want to learn more about how to work with Git in DataGrip, and how to commit, push, and work with branches, check out our tutorial named How to work with Git in DataGrip.

Download the latest DataGrip and try it out! We’d love to hear your thoughts and feedback.

To learn more about Git with all the JetBrains IDEs, watch the YouTube series covering Git Questions.

Please report issues and problems to our tracker. Thanks!

The DataGrip Team

Posted in Features, Tutorial | Tagged | Leave a comment

DataGrip 2018.3 is Released!

Hello everybody!

We are excited to release DataGrip 2018.3 today! As usual, we thank all our early adopters who have helped us make the IDE better during this release cycle. The most active ones have already got their free DataGrip subscriptions, as a token of our appreciation.Rujrn4Rw

If you wish to see the detailed overview of this update, please visit our What’s new page. Read on for a list of all the enhancements waiting for you in 2018.3.

Database objects

Cassandra database supported
— Generate SQL files for the selected objects
— Support for extensions in PostgreSQL
— Support for stored procedures in PostgreSQL 11
— Statistics in Quick Doc
Use drop cascade syntax option



Code completion

— Postfix completion
— New setting to automatically add aliases when completing table names
— Not aggregated fields in GROUP BY
— All columns list in SELECT, MERGE and INSERT INTO table variable
— Named parameters of stored procedures
— Numeric fields in SUM() and AVG()
FILTER (WHERE…) clause
— Option to Invert order of operands in auto-generated ON clause
— Window functions


Code generation

— Dialects for Live templates
— Column names hint appears automatically when using INS live template
CREATE TABLE definition for SELECT




— Intention action to Introduce table alias
— Many fixes in Extract subquery as CTE action


Code insight

— Warnings about unsafe DELETE and UPDATE
— New inspection to detect unreachable code
— Unused subquery item inspection




— Single connection mode
— Auto-reconnect after timeouts

Search and navigation

— New Search Everywhere
— Multiline TODO comments
— Multiline search in Find/Replace in Path


User interface

High-contrast color scheme
— Better UI for page size setting
— Color settings in the data source Properties dialog



You already know all of this, but still:
— Get your 30-day trial of DataGrip.
Tweet @ us!
Discuss anything in the forum.
— Report bugs to our issue tracker.

Thanks for reading this!

Your DataGrip Team
The Drive to Develop

Posted in Uncategorized | Tagged , | Leave a comment

DataGrip 2018.3 Release candidate


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

Posted in Uncategorized | Leave a comment

DataGrip 2018.3 EAP 4

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.

Screenshot 2018-11-13 09.21.05

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

Posted in Uncategorized | 2 Comments

DataGrip 2018.3 EAP 3

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

Posted in Uncategorized | 2 Comments

DataGrip 2018.3 EAP 2

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.PageSize

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

Posted in Uncategorized | 3 Comments

DataGrip 2018.3 EAP

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!


Support for:
— Stored procedures in PostgreSQL 11. DBE-6863
— ROWS FROM in PostgreSQL. DBE-7098
— Vector valued updates in SQLite. DBE-4449
— 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.

Posted in Uncategorized | 1 Comment

DataGrip 2018.2.4 is Here

When it comes to the tools of your craft, it never hurts to make sure that you are always working with the most stable version. Please meet DataGrip 2018.2.4. Inside you’ll find the following have all been fixed:

  • DBE-7023 The Find Action not working when invoked from the Welcome Screen
  • DBE-7019 The JSON exported data being formatted to scientific notation instead of flat
  • DBE-7012 The import of a custom enum type to PostgreSQL from CSV not working
  • DBE-6996 The ClickHouse datasource not properly loading after an IDE restart
  • DBE-7007 The MySQL dialect configuration change which was lost after every IDE restart
  • DBE-6939 The delayed preview of changes in the Code Style settings

That’s mostly it. Again, if you find a bug, make sure to let us know. We’ll do our best to include a fix in an upcoming update. Enjoy!

The JetBrains Team
“The Drive to Develop”

Posted in Releases | Tagged , | 19 Comments

DataGrip 2018.2.3

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.

Posted in Uncategorized | 4 Comments

DataGrip 2018.2.2: ClickHouse Support and Bugfixes

With just a few weeks since the last minor update, we’re in hurry again to bring you a fresh portion of improvements. Please welcome DataGrip 2018.2.2.

One of the highlights in this update is added support for ClickHouse (an open-source analytic DBMS for big data from Yandex). The update offers a dedicated driver, and allows you to browse the tables, views, table data, run queries, and pretty much everything (except exporting data and modifying tables).

Also, the update addresses the following issues:

  • The default row height in the Modify Table dialog is equal to the biggest row in the dialog (DBE-6443)
  • The Oracle Not-Equals operator “~=” causes a parse error (DBE-6817)
  • The SQL Server’s Filtered Index is not handled by the Modify Table action
  • Display schema names in the editor tabs if the Multiple Schemes checkbox is enabled (DBE-6693)
  • The Go to File action included non-project files (DBE-5459)
  • The formatter for Sql Server obscured spaces before and after the dot between the schema and table names (DBE-6874)
  • The new line concatenation not supported for PostgreSQL (DBE-6853)
  • Multiple JOINs with USING for MySQL sometimes were not resolved correctly in the editor (DBE-6844)

Last but not least, the update fixes a few performance issues related to VCS (file scanning).

That’s mostly it. Hope you’ll enjoy these improvements. The update available within the IDE (if you’re running DataGrip 2018.2.1), from the Toolbox App, and from the DataGrip website.

P.S.: In case you have an issue, a question, or a feature suggestion, make sure to share it here in the comments or report it directly to our issue tracker.

The JetBrains Team
“The Drive to Develop”

Posted in Features, Minor updates | Tagged , , | 2 Comments