#26540: Can't run tests without "default" connection set
-------------------------------------+-------------------------------------
Reporter: marcinn | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by claudep):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The fact that the `default` database is mandatory is documented in the
DATABASES setting
(https://docs.djangoproject.com/en/1.9/ref/settings/#databases).
There are still places in Django core code depending on a `default`
database (See #13528 for example). We should hopefully get rid of them at
some point, but we aren't there yet.
As a workaround, did you try to set a dummy backend to the `default`
alias?
--
Ticket URL: <https://code.djangoproject.com/ticket/26540#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.ca27b88dc3ea8bfaf7d021062f1f37b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
