Query Consoles Are Coming Back
Hi DataGrip and Database Tools community,
Shortly after the 2025.3 release, your feedback made it clear that the redesigned workflow for query files and query consoles introduced issues in several important scenarios, especially when working with global data sources.
After reviewing the impact, we’ve decided that the best course of action is to revert this change in both DataGrip and the Database Tools plugin for JetBrains IDEs, rather than attempt incremental fixes while more users continue to update and encounter problems.
The rollback will be included in the upcoming 2025.3.1 release arriving later this week.
This affects only those who updated to 2025.3. If you haven’t updated yet, your workflow remains unchanged. If you have, we recommend updating to 2025.3.1 as soon as it becomes available to minimize the gap between the previous and restored behavior.
What’s changing:
- Query consoles return as the default workflow, working exactly as they did before 2025.3.
- Query consoles saved before the migration will appear in the same locations as before.
- Query files created during or after the migration will remain available. You can handle them in several ways:
- Delete query files you don’t need. In DataGrip, their default location is the /queries folder in the Files tool window. In other IDEs, their default location is the /.idea/queries mvb directory in the Project tool window.
- Convert query files you want to keep into query consoles. To do so, move them to the appropriate data source node under Scratches and Consoles | Database Consoles (in the Files tool window in DataGrip or in the Project tool window in other IDEs).
- Keep your query files for now. We plan to bring back an improved query file workflow early next year so it can work alongside query consoles in a more intuitive and flexible way.
A note from the team
We apologize for the inconvenience and disruption caused by this change. We hold ourselves to a zero-regression standard, and this release did not meet it. That responsibility is on us, and our focus now is on minimizing the impact and restoring your workflow as quickly as possible. Your trust means a lot, and we’ll continue doing our best to earn it.
Although we are reverting this change for now, our long-term goal remains unchanged: to improve this core workflow and make it more intuitive for both new and experienced users. We will move forward more carefully, and future updates will be more flexible and less disruptive, even if that requires more time and effort on our side.
If you have any comments or encounter any issues, please contact us through our issue tracker or support channels.
Best regards,
The DataGrip team
Subscribe to DataGrip Blog updates
