#16752: Multi-db without a 'default' database
-------------------------------------+-------------------------------------
Reporter: jdunck | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: 1.3 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Design | Keywords:
decision needed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by russellm):
* stage: Unreviewed => Design decision needed
Comment:
The intention at time of design was that there would always need to be a
default database. This was done mostly as a migration aid -- historically,
django.db.connection was your path to the connection; moving to
django.db.conections meant that a lot of older code wouln't work, so the
older alias was retained, using the 'default' alias. I can see how this
could be relaxed so django.db.connection only exists if you actually
define a 'default' alias; I'd need to see a deeper analysis of the
implications of this change to make a definitive call.
The validation problem has been logged previously (#13528) -- it's not an
easy one to fix in a backwards compatible fashion. This may end up being
the biggest reason why the default alias can't be removed entirely.
--
Ticket URL: <https://code.djangoproject.com/ticket/16752#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
