#36003: Add `connection_closed` or `pre_connection_closed` and
`post_connection_closed` signals
-------------------------------------+-------------------------------------
Reporter: Tomasz | Owner: Tomasz Wójcik
Wójcik |
Type: New | Status: assigned
feature |
Component: Database | Version: dev
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------+-------------------------------------
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.
https://github.com/django/django/blame/6f38697f90a14f1450a71c1e40aea0f5df7dca86/django/db/backends/signals.py
I'd like to create a `connection_closed` signal and connect it here
https://github.com/django/django/blob/6f38697f90a14f1450a71c1e40aea0f5df7dca86/django/db/backends/base/base.py#L314
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/36003>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193b9ee8d64-ee50b92a-b3cb-4a39-803c-9f3c491d7fab-000000%40eu-central-1.amazonses.com.
