#22487: Moving from initial_data to data migrations stops test data persisting
-------------------------------------+-------------------------------------
Reporter: andrewgodwin | Owner:
Type: Bug | andrewgodwin
Component: Testing framework | Status: closed
Severity: Release blocker | Version:
Keywords: | 1.7-beta-1
Has patch: 0 | Resolution: fixed
Needs tests: 0 | Triage Stage: Accepted
Easy pickings: 0 | Needs documentation: 0
| Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by andrewgodwin):
Yes, you should not be using TransactionTestCase unless you're very sure
you want to use it (i.e. you're testing transaction handling).
As for your traceback, it looks like you have a custom user with some
extra ForeignKeys that aren't being populated right. Does normal use of
loaddata/dumpdata work with your app and this model?
--
Ticket URL: <https://code.djangoproject.com/ticket/22487#comment:23>
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/070.55449815d848bffc93c555a6931da0cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.