Database Tool Window: Re-execution Guard for Uncertain Write Outcomes

Direct Answer

No. PyCharm's Database tool window (shared across all IntelliJ-based IDEs) does not surface a confirmation dialog, inline warning, or per-session "last write status" indicator when you re-execute a write statement after a timeout or lost connection. There is also no configuration flag to enable such a guard. The only way to add this behavior today is to write a custom plugin using the Database plugin API.

Current Behavior

• Each Run action sends the statement exactly once. The IDE does not automatically retry on socket error or query timeout.
• After a network interruption or timeout, the console shows an error but does not record whether the server committed, rolled back, or left the transaction in an unknown state.
• Pressing Run again on the same statement sends it a second time with no duplicate detection, no warning, and no status badge (committed/rolled back/unknown) in the Sessions or Output tabs.
• Settings → Tools → Database → General / Console / Execution contains no checkbox for "re-execution guard," "write status tracking," or "duplicate warning."

Open Questions Addressed

1. Confirmation dialog / inline warning? Not present. The decision to re-run is entirely manual.
2. Per-session "last write status" indicator? Not present. No badge appears in the tool window, result pane, or status bar.
3. Configuration flag or plugin extension point? No configuration flag exists. The Database plugin API (com.intellij.database.console, com.intellij.database.execution) exposes execution callbacks (ConsoleExecutionListener) and message-bus topics, so a custom plugin could track outcomes and surface a warning—but this requires plugin development and is not available out of the box.

Practical Workarounds

• Use explicit transactions (disable Auto-commit). If the session is still alive after a timeout, you can issue ROLLBACK before deciding whether to retry.
• Rely on schema-level idempotency: unique constraints, INSERT ... ON CONFLICT (PostgreSQL), MERGE (Oracle/SQL Server), or application-generated idempotency keys.
• Query the target table after reconnecting to verify the actual state before re-executing.

Verification Steps (PyCharm 2024.x)

1. Open Settings → Tools → Database → General / Console / Execution and confirm no guard-related checkboxes exist.
2. Run a long UPDATE, disconnect the network (or set a short statement timeout), then press Run again on the same statement. Observe that no confirmation dialog appears and the statement is sent again.
3. Check the Sessions/Output tabs after the timeout: the prior execution shows an error but no committed/rolled-back/unknown badge.

Assumptions & Uncertainty

Behavior is identical across PyCharm Professional, IntelliJ IDEA Ultimate, DataGrip, and other IDEs sharing the same Database plugin. Minor UI differences may exist between 2024.1 and 2024.3, but the core execution model and absence of guards are consistent. If you are on a 2025 EAP build, re-check the Settings panels—new features could appear.