Allow to drop databases with open connections
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
During development it happens that I may iterate quickly on database changes.
Dropping the database is a common occurrence during this, while a dev server might still be connected to the schema; or a test suite is holding on to a connection.
It would be nice that I could tell Postico to drop the database, regardless of the active connections.
## What did you do?
- I started the "Delete..." procedure on a database
- I typed in the "DROP DATABASE" command
- Clicked the "Delete" button
## What did you expect to happen?
- Being warned that there are open connections, and have the option to proceed.
## What actually happened?
- I was told there where open connections, and that deleting is not possible.
## What software versions are you using?
Postico version:
```1.5.17 (7585)```
PostgreSQL version:
```PostgreSQL 12.4 (Debian 12.4-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit```
Contributor guide
No contributing guide indexed for this repository
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
Start with the Delete... procedure and the PostgreSQL DROP DATABASE handling described in the issue. Trace how active connections currently prevent deletion; done means the user is warned about open connections and can choose to proceed with dropping the database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100