#22837: Migrations detect unnessecary(?) changes
-------------------------------+--------------------------------------
Reporter: valberg | Owner: nobody
Type: Uncategorized | Status: closed
Component: Migrations | Version: 1.7-beta-2
Severity: Normal | Resolution: invalid
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 mjtamlyn):
* status: new => closed
* resolution: => invalid
Comment:
This is by design. There are several reasons, not least of which for me
that datamigrations at points in history need to have a full accurate
representation of the models, including all their options not just those
which affect the database.
[Bendavis: if, as I read from your comment, you believed this was not a
valid bug, you are welcome to close the ticket yourself]
--
Ticket URL: <https://code.djangoproject.com/ticket/22837#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.4334008008220e2cdf2cb3fca6aff82e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
