#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
-------------------------------+--------------------------------------
Changes (by timo):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I think this is a duplicate of #22487 which was resolved just a couple
days before your report so perhaps you didn't see it. Could you confirm?
That said, I believe we still need to update the documentation as you
noted.
--
Ticket URL: <https://code.djangoproject.com/ticket/22834#comment:1>
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.f6687c80a8f3e63c76622b0a69247584%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
