#27772: Multiple Database without Default
-------------------------------------+-------------------------------------
Reporter: Sammie S. Taunton | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: database, multiple | Triage Stage:
database, default database, | Unreviewed
database router |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
Hi, in a case like this, it's better to ask for help on our
[wiki:TicketClosingReasons/UseSupportChannels support channels] until you
confirm you've identified a bug. For best results, please include a sample
project that reproduces the issue. If you confirm that Django is at fault,
please reopen with details. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/27772#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.8b67d4cc6991227d8eb83bf96aec63e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
