#22837: Migrations detect unnessecary(?) changes
-------------------------------+--------------------------------------
Reporter: valberg | 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 bendavis78):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
From what I understand, the migrations system doesn't discriminate between
field attributes, so if any attribute changes (even ones like help text),
the auto-detector will treat it like any other change. There's currently
no elegant way to predict how field attributes might affect the migration
states. See #21498 for more discussion on the subject.
--
Ticket URL: <https://code.djangoproject.com/ticket/22837#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/065.8c9ea104492708a20278423839d59a12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
