2025.1 eap 内部版本号 251.20015.44

已发布: 2025年2月10日

无需订阅

下载

DataGrip Early Access Program

打造出色工具的秘密在于倾听使用它们的开发者的意见。我们的抢先体验计划让社区可以从最初阶段就参与产品讨论并影响开发计划。

DataGrip 正处于积极开发阶段,我们十分欢迎您提供反馈。请使用 DataGrip 问题跟踪器报告 bug 和提出功能建议。或者在X 上与我们联系

为什么您应该试试 EAP 版本?

抢先体验计划让您可以评估全新功能以及将添加到下一版本中的现有功能的许多重要错误修正。您可以将 DataGrip EAP 与稳定的 DataGrip 一同安装并获取定期更新。

这是产品的抢先体验版本

您明确确认此版本的产品可能不可靠,无法按预期工作,并且可能包含错误。使用 EAP 产品的风险由您自己承担。

使用 Toolbox App 轻松下载 DataGrip 及其未来更新

版本信息版本亮点

2025.1 eap 内部版本号 251.20015.44

已发布: 2025年2月10日

无需订阅

下载

Hello! We are starting the EAP program for version 2025.1. This is the perfect opportunity to try new features before the official release and share your feedback with us.

Introspection by levels for MySQL and MariaDB

We're continuing our work to enhance introspection performance. Starting from 2025.1, there will be different introspection levels for MySQL and MariaDB, adjusting the amount of metadata that gets loaded depending on the size of your database. In other words, we won't load all the metadata if your database is large. This will greatly reduce introspection time and allow you to start working with newly connected data sources right away.

What are the introspection levels?

Level 1 Level 2
  • Icon:
  • Metadata loaded: Everything except the source code of functions, procedures, views, events.
  • Main missing features: Find Usages, the ability to search in the text of views and procedures.
Level 3
  • Icon:
  • Metadata loaded: Everything, just as in previous versions.
  • Main missing features: None, all features are working as expected.

DataGrip now prioritizes the user experience and performance over the comprehensiveness of functionality. The default introspection level value is set to Auto select, which means that DataGrip uses an internal heuristic to detect how much metadata needs to be loaded.

For now, this heuristic looks like this:

Current schema:

  • Level 1 when the number of schema objects is greater than 3000.
  • Level 2 when the number of objects with sources is greater than 500.
  • Level 3 in all other cases.

Other schemas:

  • Level 1 when the number of schema objects is greater than 300.
  • Level 2 when the number of objects with sources is greater than 50.
  • Level 3 in all other cases.

We are considering whether to adjust the heuristic or even make it customizable.

By default, DataGrip will automatically set the introspection level. If you want to restore DataGrip's previous behavior, go to Data Source properties | Options | Introspection | Default level and select Level 3.

You can also manually select a level if you think that will maximize DataGrip's performance for your use cases.

To summarize, you should no longer experience any significant performance problems related to MySQL / MariaDB introspection. If you do, please let us know about them via our issue tracking system.

Attached schemas in the Explain with AI chat

Explanations of your queries are more effective with the full context! Now, when you ask AI Assistant to explain a query, the corresponding schema is automatically attached to the chat.

[Oracle] The ability to connect with a specific role

DBE-96 has been fixed. It's not every day we close a ticket with an ID less than 100! Starting with 2025.1, you can connect to Oracle and define the specific role for the connection in the connection dialog.

Simply select the desired role from the Authentication drop-down list:

The ability to download drivers from Maven

Version 2025.1 allows you to add custom repositories for downloading drivers. To do so, add the repositories you need to the mirrors attribute of the HOME_PATH/.m2/settings.xml file.

Important fixes

  • DBE-9626: The color used for a data source is now applied to the attached file tab.
  • DBE-21934: Value completion in the data editor inserts the correct string.
  • DBE-18569: The Cancel button works as intended when downloading drivers.
  • DBE-15201, DBE-20350: [SQL Server] Stored procedures and system objects are qualified with the relevant schema names if the corresponding setting is enabled.
  • DBE-22250: [Snowflake] It is possible to remove Role and Schema after they've been added to the connection parameters.
  • DBE-21514: [Oracle] Aliases are inserted for code completion of synonyms.
  • DBE-17959 [PostgreSQL] UNIQUE NULLS NOT DISTINCT is now supported.