#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
-------------------------------------+-------------------------------------
Comment (by Ryan Cheley):
Replying to [comment:6 Natalia Bidart]:
Sounds good. I'll get to working on this 😀
> Hey Ryan, while I agree that the docs have changed/improved, I think
this ticket is about doing the cleanup to actually remove the need to
declare a `default` database (which should also avoid the need to define a
`default` key, even if empty, in the `DATABASES` dict).
>
> So from my understanding, this ticket is still valid and needs
addressing.
--
Ticket URL: <https://code.djangoproject.com/ticket/16752#comment:7>
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/0107018cdf716eec-46ba5992-978a-4e4a-8005-d884cbc5ba96-000000%40eu-central-1.amazonses.com.
