Opened 6 days ago
Closed 6 days ago
#36003 closed New feature (wontfix)
Add `connection_closed` or `pre_connection_closed` and `post_connection_closed` signals
| Reported by: | Tomasz Wójcik | Owned by: | Tomasz Wójcik |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
Currently I'm facing an issue with stale DB connections. It's probably related to my setup. Having connection_closed signal would simplify my debugging process.
Since 2009, there's connection_created signal.
I'd like to create a connection_closed signal and connect it here
This way the connection can be accessed right before closing it.
I'd be happy to implement it. Let me know what you think.
I'm also open to pre_connection_closed and post_connection_closed. Even though not many people will ever use it, I can imagine wanting both in different cases.
Note:
See TracTickets
for help on using tickets.
Can you propose and discuss the idea with the community on the Django Forum? There you'll reach a broader audience and receive additional feedback.
If the community agrees with the proposal, please return to this ticket and reference the forum discussion so we can re-open it. For more information, please refer to the documented guidelines for requesting features.