#23979: Multi-db test fails to run because of fixture containing M2M field
(dumped
with --natural-foreign)
-------------------------------------+-------------------------------------
Reporter: ej | Owner: nobody
Type: Bug | Status: new
Component: Core | Version: 1.7
(Serialization) | Resolution:
Severity: Normal | Triage Stage:
Keywords: multi-db, m2m, | Unreviewed
fixture, natural key | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by ej):
I have tried forcing `db_for_write()` and `db_for_read()` to return
'default' database, but that doesn't work either. If you look at that the
particular code I highlighted above,
`self._databases_names(include_mirrors=False)` returns all databases in my
case, given that my test case is configured with `multi_db = True`.
Regardless of `db_for_read` and `db_for_write`, fixture is installed for
both databases.
--
Ticket URL: <https://code.djangoproject.com/ticket/23979#comment:3>
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/060.929a0024e484cd98a317fc54c15d91f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
