#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 timgraham):

 The issue seems to be fixed if you rename the fixtures file to
 `permset_test.default.json` but keep `fixtures = ['permset_test.json']` in
 the `TestCase`.  `self.assertEqual(PermSet.objects.count(), 1)` passes in
 the test. Does this resolve your issue?

--
Ticket URL: <https://code.djangoproject.com/ticket/23979#comment:6>
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.9455d5c51a3b71fe69458e765bfa52b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to