#36505: Allow overriding default database with a `db.override` contextmanager
-------------------------------------+-------------------------------------
Reporter: rockisch | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: database router | Triage Stage:
contextmanager | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => wontfix
* status: new => closed
Comment:
Hello, thank you for the careful suggestion - please can you raise this on
the [https://github.com/django/new-features/issues new feature tracker]?
We are following a process where all new feature ideas should first be
proposed and discussed with the community
I'll close the ticket for now, but 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
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features the documented guidelines for requesting
features]. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/36505#comment:2>
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/010701980cd7db94-7fa54c72-0c51-41e2-a79e-50e7d0fcfc74-000000%40eu-central-1.amazonses.com.
