#26197: DEFAULT_DB_ALIAS in settings
-------------------------------------+-------------------------------------
Reporter: marcinn | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Sorry, but I can't unilaterally accept design decisions like this. That's
why it needs discussion on the mailing list. For example, the original
authors of multi-database support may have considered and rejected the
idea. As mentioned on the related ticket, we do our best to avoid new
settings so any proposal for that needs a strong justification and a
discussion.
--
Ticket URL: <https://code.djangoproject.com/ticket/26197#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.f9071a3576e20730f7792fc0b08c0235%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
