#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):
It happens on DBs without transactions _and_ with `TransactionTestCase`,
because the latter is not enclosed in a transaction and so we can't roll
it back, unfortunately. This is why you should avoid `TransactionTestCase`
unless you really need it :)
Is it possible that you could reduce the problem to a couple of models and
a migration so I can replicate it? Failing that, if you're comfortable, a
larger slice/the whole project would work (I'm happy to directly negotiate
access so it's not in public if the project isn't open source).
--
Ticket URL: <https://code.djangoproject.com/ticket/22487#comment:25>
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.230d336c85f6078a80caf035c3b0f771%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
