#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):
I asked Alex Gaynor, the original author of multi-db support and he said,
"Probably a bad idea IMO, I think it makes things much more confusing
cross-projects and the benefit isn't clear to me. There's no technical
reason you can't do it though."
--
Ticket URL: <https://code.djangoproject.com/ticket/26197#comment:6>
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.d5ebf0a3851dc496a0ad67f33a5f1aa4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
