#22834: The builtin migrations being the only way to do migrations breaks data
migrations/fixtures in tests
-------------------------------+--------------------------------------
Reporter: gc@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.7-beta-2
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
-------------------------------+--------------------------------------
Comment (by anonymous):
I think that's a terrible solution, though. :-( The simple solution would
be to have an argument for tests, that makes it not flush. We worked
around by defining our own flush that does nothing, but that's an ugly
hack.
Additionally, the solution is not only slow and ugly, but broken since it
makes you force no transactions (no idea what the other implications of
this are)
--
Ticket URL: <https://code.djangoproject.com/ticket/22834#comment:2>
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/071.8b9d2dbbd56e2404a017c67487643bb7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
