#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 marcinn):
Right. But this is not about design. Im not taking about enhancement of
multi db support, but just about one setting. I will not discuss on
mailing list because it is a waste of time. My suggestions, like a
model.reload(), must wait approx 7 years for your agreement. My endless
discussions about disabling migrations are next example. And so on...
I would like to make more contributions for Django, including patches and
tests, but I can't pass through idea-wall... My English is too bad for
this, I think.
So maybe tell me, please, what consequences might be after changing
default db alias? How big is risk? Is it worth starting new discussion?
I'm not asking about guys you've mentioned.
--
Ticket URL: <https://code.djangoproject.com/ticket/26197#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.4eed0f65b67a4a58de584f14e2ad7b56%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
