pgadmin-org / pgadmin-org/pgadmin4
PGAdmin should attempt to refresh the database if the user tries to interact with a database that's disconnected
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- postgresql, python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100