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

Context

PyCharm's Database tool window executes SQL statements exactly as submitted and does not automatically retry a write after a network interruption or query timeout. Autocommit and manual commit/rollback controls are available, but the IDE provides no built-in idempotency token, deduplication table, or replay protection for INSERT, UPDATE, or DELETE statements.

Unresolved Behavior

When a write statement times out or the session drops, the transaction outcome at the server remains unknown until the user reconnects and queries the target table. Re-executing the same statement in the console can therefore duplicate the change unless the database schema (for example, a unique constraint) prevents it. Current versions leave the decision to re-run entirely to the user, with no warning that the prior execution may have committed.

Open Questions

1. Should the Database tool window surface a confirmation dialog or inline warning when the user attempts to re-execute a write statement whose previous execution ended in a timeout or lost connection?
2. Would a per-session "last write status" indicator (committed, rolled back, unknown) reduce accidental duplicates without adding friction for intentional retries?
3. Is there a configuration flag or plugin extension point that could enable such a guard without modifying the core console behavior for all users?