DataGrip–Docker Compose Auto-Refresh Timing Interoperability

DataGrip's schema synchronization relies on an auto-refresh timer that polls the database metadata at a user‑configured interval, with a default of five seconds. When a Docker Compose service hosts the database, changes made outside the IDE—such as migration scripts applied via the container's command line or external tools—must become visible in the IDE's schema tree through this refresh cycle. The precise interaction between the timer interval, Docker Compose port mappings, and the JDBC driver's connection lifecycle remains an open design question, particularly when multiple console sessions share a single pooling driver or when the service is restarted.

A key constraint is that the auto-refresh behavior does not automatically account for container lifecycle events; a service restart or port reassignment may invalidate existing JDBC URLs until the data source is re‑evaluated. Additionally, disabling the timer requires manual schema tree refreshes, creating a potential workflow disconnect for developers who expect real‑time synchronization. The extent to which adjusting the refresh interval mitigates stale‑schema symptoms across typical development cycles is not formally documented.

Does DataGrip's auto-refresh timer reliably detect schema changes introduced inside a Docker Compose service when the interval is set to less than five seconds? Can a pooling driver such as HikariCP maintain consistent connection state across multiple console sessions targeting the same Compose service without manual pool reset? How does a container restart or port remapping affect the validity of the stored JDBC URL and the subsequent schema refresh outcome?