2025.1 eap build 251.20015.44
Publiée: 10 février 2025
Aucun abonnement requis
DataGrip Early Access Program
Le secret de la création d'outils pour les développeurs réside dans une écoute attentive. Notre programme d'accès anticipé (EAP) permet à la communauté de participer aux discussions sur nos produits et d'influencer la planification du développement dès les premières étapes.
DataGrip est en cours de développement actif, et nous apprécions vraiment vos retours. Veuillez utiliser notre outil de suivi d'incidents DataGrip pour signaler les bugs et suggérer de nouvelles fonctionnalités, ou contactez-nous sur X !
Pourquoi essayer les builds EAP ?
Le programme d'accès anticipé vous permet d'évaluer les toutes dernières fonctionnalités ainsi que les corrections de bugs qui seront ajoutées à la prochaine version majeure du produit. Vous pouvez installer DataGrip EAP en parallèle de l'installation stable de DataGrip et obtenir régulièrement les mises à jour pour les deux versions.
Informations du build | Principales fonctionnalités de ce build |
---|---|
2025.1 eap build 251.20015.44 Publiée: 10 février 2025 Aucun abonnement requis | 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 MariaDBWe'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
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:
Other schemas:
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 chatExplanations 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 roleDBE-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 MavenVersion 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 Important fixes
|