#25601: makemigrations create unnecessary migrations
-------------------------------+--------------------
Reporter: vstoykov | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
When verbose name of model or field is changed or some validator
added/removed this creates unnecessary migrations. These attributes are
not related to database at all and this will create extra migrations which
then need to rebuild the state every time when migrations are run on
validations are processed.
This is extra overhead that potentially can slow all tasks related to
migrations, and also extra noise in version control and also is very
annoying. This state (verbose name, validators and potentially other
attributes) is not needed for datamigrations also.
I saw people to complain about speed of the new migrations framework and I
think that this can help at least a little.
This is not tested it's jut my hypothesis.
--
Ticket URL: <https://code.djangoproject.com/ticket/25601>
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/051.9dc7c92a38f355ea06e710f61360fe4d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
