ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #datagrip
DataGrip’s Local History feature automatically tracks every change you make to SQL files and console queries. This article shows how to view, compare, and revert those snapshots, the limits of the feature, and when you should still use a version‑control system.
Stop relying on manual search-and-replace for database schema changes. Learn how to use DataGrip's refactoring engine to safely rename columns and update dependent views and foreign keys.
Decide whether to expose a database port with SSL/TLS, tunnel through a bastion host, or combine both in DataGrip.
DataGrip's Database Diagrams reverse-engineer ER views from system catalogs—no data scans. Learn incremental workflows, cross-database migration diffs, refactoring previews, and the permission gotchas that break relationship detection.
Use DataGrip's schema comparison and SQL Preview to inspect generated ALTER, CREATE, and DROP statements before applying changes to live databases.
Stop guessing if your SQL migrations will fail. Learn how to use DataGrip's Attach Directory feature to get dialect-aware validation and ordered execution for Flyway and Liquibase scripts.
Keep DataGrip’s page‑size limit enabled to avoid loading millions of rows into memory, and tune the JDBC fetch size per driver for smooth paging.
When database objects disappear in DataGrip, introspection failure is often the culprit. Follow this diagnostic guide to identify and resolve issues caused by metadata caching, driver mismatches, schema filtering, or permission gaps.
Stop guessing what changed in your database. Learn how to use DataGrip's Compare Structures tool to identify schema drift and generate safe DDL migrations.
mysql
postgresql