PGAdmin should attempt to refresh the database if the user tries to interact with a database that's disconnected

Open
#9,700 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
postgresql, python
Domain
databases

Research direction

No files, tests, or entry points are named. Reproduce the object-view interaction after dropdb/createdb or a VPN interruption, then trace how pgAdmin handles a disconnected database; done means an optional reconnect attempt restores interaction without requiring a manual refresh.

Written by the indexing model from the issue text.

Description

Feature

As a backend developer I often dropdb, createdb + repopulate when I come back to the object view I have to right click and refresh, even though I have a new database with exactly the same name as the previous one.

It would be good if pgadmin4 could (optionally) try and reconnect at least once - if I do something in the object view + it's lost it's connection.

This would be good in other work-related circumstances too - there's a VPN and so I periodically have to reconnect things, and pgadmin is yet another place I have to do a reconnection ceremony that I'd like to have automated.

Dominant language
Python
Stars
3.9k
Forks
922
Avg merge
2d 3h
Merged PRs (30d)
33

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pgadmin-org/pgadmin4

All issues in pgadmin-org/pgadmin4

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.