#16752: Multi-db without a 'default' database
-------------------------------------+-------------------------------------
Reporter: Jeremy Dunck | Owner: Ryan
| Cheley
Type: Bug | Status: assigned
Component: Database layer | Version: 1.3
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Ryan Cheley):
* owner: nobody => Ryan Cheley
* status: new => assigned
Comment:
The docs no longer have the statement mentioned in the ticket (it seems to
be have removed in
[https://github.com/django/django/blob/stable/1.5.x/docs/topics/db/multi-
db.txt Django 1.5] but was in
[https://github.com/django/django/blob/stable/1.4.x/docs/topics/db/multi-
db.txt Django 1.4]).
Django 1.4 was the last time this seems to have been in the docs, and
Django 1.4 had and end to extended support in October 1, 2015
Given that, I'm wondering if this can be marked as closed.
--
Ticket URL: <https://code.djangoproject.com/ticket/16752#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cc0e51ed6-eb2eee6f-cf6d-4359-a909-f3750ea7ea51-000000%40eu-central-1.amazonses.com.
