#22834: The builtin migrations being the only way to do migrations breaks data
migrations/fixtures in tests
-------------------------------+--------------------------------------
Reporter: gc@… | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => duplicate
Comment:
Thanks for the kind words. I gather from your comment that the issue you
reported is fixed, even though you disagree with the fix.
I'm not sure what the issue with transactions is. Since it's a different
one, it belongs to a separate ticket. I'll need a bit more information to
understand it.
Finally, if you can provide a better and simpler solution that still meets
all the constraints discussed in #22487, including the mailing-list thread
linked to in the first comment, please open a new ticket and submit a
patch or a pull request! Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/22834#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/071.f20fd87573c04cd0218d029e4506d63e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
