#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 Tim Graham):
Option one, although the database shouldn't be treated as the default.
Instead the developer must route each query as explained in the ticket
description. Comment 2 describe the issue and the potential roadblocks
fairly well. I think it will be difficult. Trying to solve #13528 could be
a first step.
--
Ticket URL: <https://code.djangoproject.com/ticket/16752#comment:9>
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/0107018ce11ddfcd-c86ea952-e0ce-4f6c-8d92-68181c4c7909-000000%40eu-central-1.amazonses.com.
