{"id":156593,"date":"2021-06-24T10:26:14","date_gmt":"2021-06-24T09:26:14","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=datagrip&p=156593"},"modified":"2025-09-22T07:58:40","modified_gmt":"2025-09-22T06:58:40","slug":"datagrip-2021-2-eap-2","status":"publish","type":"datagrip","link":"https:\/\/blog.jetbrains.com\/en\/datagrip\/2021\/06\/24\/datagrip-2021-2-eap-2","title":{"rendered":"DataGrip 2021.2 EAP 2"},"content":{"rendered":"\n

Hello! Another EAP build for 2021.2 is available! We would appreciate it if you would try it out and share your feedback with us. <\/p>\n\n\n\n

New location for projects<\/h2>\n\n\n\n

In DataGrip, projects are now located by default in the same place as they are in all other IntelliJ-based IDEs \u2013 in the user’s home folder, inside the DataGripProjects<\/em> subfolder.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Your project in DataGrip is a complex of your data sources, console and scratch files, and attached folders. They were previously stored in the configuration folder<\/a>, meaning that each time you updated your IDE, the projects were copied, along with IDE settings. This sometimes caused the data source list to become empty. This problem has been solved, and now DataGrip behaves consistently with other IDEs.<\/p>\n\n\n\n

Due to errors in project migration, those who used the first EAP build might have lost their Favorites, Bookmarks, Run Configurations, or data about virtual foreign keys. To restore them, please migrate from the previous version again. The details are described here: DBE-13410<\/a>.<\/p>\n\n\n\n

[MongoDB] Completion of fields and operators<\/h2>\n\n\n\n

Our code completion has now come to the MongoDB console. <\/p>\n\n\n\n

Fields<\/h3>\n\n\n\n

What can be completed now:<\/strong><\/p>\n\n\n\n

Fields: <\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Nested fields:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Fields inside aggregation expressions<\/a>:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Additional information:<\/strong><\/p>\n\n\n\n

\u2013 Fields at the top level have a higher priority level than operators, and vice versa for nested fields.<\/p>\n\n\n\n

\u2013 Field completion works in all methods except for db.collection.aggregate ([…])<\/em>.<\/p>\n\n\n\n

\u2013 Completion works in string literals, as well.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

\u2013 In most cases, completion works when using parameters in scopes:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Operators<\/h3>\n\n\n\n

Completion works for:<\/strong><\/p>\n\n\n\n

Query operators<\/a><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Projection operators<\/a><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Update operators<\/a><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Aggregation stages<\/a><\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Separate folders for functions and procedures<\/h2>\n\n\n\n

If you turn on the Separate Procedures and Function<\/em> option in the settings of the database explorer (the gear icon), it will immediately take effect! For now, this is available for Microsoft SQL Server, Oracle, and PostgreSQL.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Natural sort order for database objects<\/h2>\n\n\n\n

If you turn off the Sort Alphabetically<\/em> option in the database explorer settings, the natural sorting for objects is applied. <\/p>\n\n\n\n

Sort Alphabetically<\/em> is off:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Sort Alphabetically<\/em> is on:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

[SQL Server] Linked Servers<\/h2>\n\n\n\n

This is not full support as you would expect, because metadata is not available for objects in linked servers. Linked servers are shown in the database explorer, and the DDL for their creation can be generated.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Code completion quality<\/h2>\n\n\n\n

We’ve fixed several bugs to improve the quality of code completion:<\/p>\n\n\n\n

DBE-10515<\/a>, DBE-2212<\/a>: The objects from the schema of the current context have higher priority in the code completion list.<\/p>\n\n\n\n

DBE-7781<\/a>: Automatic alias doesn’t appear when it is not needed.<\/p>\n\n\n\n

DBE-12018<\/a>: Table qualification in JOIN completion works.<\/p>\n\n\n\n

DBE-12479<\/a>: The priority of ASC\/DESC inside the ORDER BY clause has been increased.<\/p>\n\n\n\n

DBE-13341<\/a>: [PostgreSQL] Completion in GRANT\/REVOKE statements works.<\/p>\n","protected":false},"author":395,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","categories":[826,89],"tags":[6569,1334,2655,3834],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/datagrip\/156593"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/datagrip"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/types\/datagrip"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/users\/395"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/comments?post=156593"}],"version-history":[{"count":3,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/datagrip\/156593\/revisions"}],"predecessor-version":[{"id":641682,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/datagrip\/156593\/revisions\/641682"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/media?parent=156593"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/categories?post=156593"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/tags?post=156593"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/en\/wp-json\/wp\/v2\/cross-post-tag?post=156593"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}