DataGrip 2025.1 is out!
Schema context for AI-based error explanations, introspection by levels for MySQL and MariaDB, Maven
mirror support, grid UI improvements, and more!
Free 30-day trial available
Explanations are more effective when they use all the relevant context. Now, when you ask AI Assistant to explain a query, the corresponding schema is automatically attached to the chat!
The AI model selection in the chat has just been expanded! Now, you can take full control of your AI experience by choosing from the latest and most advanced language models, including:
With this release, JetBrains AI Assistant has received a major upgrade, making AI-powered development more accessible and efficient. All JetBrains AI features are now accessible for free in our IDEs, with unlimited use for some, such as unlimited code completion and local model support, and limited credit-based access to others. We're also introducing a new subscription system that makes it easy to scale up as needed with the AI Pro and AI Ultimate tiers.
We’re continuing our work to enhance introspection performance. Now, there are different introspection levels for MySQL and MariaDB, and the amount of metadata that gets loaded will automatically be adjusted depending on the size of your database. In other words, we won't load all the metadata if your database is large. This will significantly reduce introspection time and allow you to start working with newly connected data sources right away.
DataGrip now prioritizes 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:
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: Everything.
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 or MariaDB introspection. If you do, please let us know about them via our issue tracker .
This JDBC driver was initially developed by the Rider team. From this release, it's also available in DataGrip.
The main feature of this driver is its support for the shared memory protocol. This protocol is used by clients to connect to the SQL Server instance that is running on the same machine. SQL Server’s shared memory protocol is the simplest protocol, as it has no configurable settings that need to be tuned in order to use it.
DBE-96 has been fixed. It’s not every day we close a ticket with an ID number lower than 100! Now 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.
We have implemented support for the use of tildes (~
) in path fields for
SSL certificates
and BigQuery
key files. Now, you can use the character to specify directories in the Data Sources
and Drivers
dialog.
To do that for your SSL connection, open the dialog by pressing Cmd+; (macOS) or
Ctrl+;
(Windows/Linux)
and select the data source you want to change the settings for. Then open the
SSH/SSL tab and
navigate
to the SSL section.
This version allows you to add custom repositories for downloading drivers. To do so,
add the
repositories you need to the mirrors
attribute of the
${user.home}/.m2/settings.xml
file.
DataGrip has a setting that limits the amount of data that’s loaded in each cell. This is designed to improve performance when there is too much data in your tables.
But in some cases, you need to load all of the data, and now that’s possible! To do this, hover over the cell and click Load Full Cell on the quick actions popup toolbar.
For PostgreSQL, MySQL, and MariaDB spatial databases, DataGrip can now correctly display raw geo-type values in the grid.
To see timestamps presented in microseconds, simply choose the corresponding display type by right-clicking the column header and navigating to Change Display Type.
When creating temporary tables, DataGrip now suggests you switch to Single session mode. This mode will allow you to see these tables in the database explorer.
UNIQUE NULLS NOT DISTINCT
is now supported.
ASOF JOIN
syntax is now correctly interpreted.
DATETIME
field data is now stored in the TEXT
format by
default.
JOIN
autocompletion now works as expected.
Free 30-day trial available