#29899: Adapt the auto-detector to detect changes from model states instead of
model classes
------------------------------------------------+------------------------
Reporter: Simon Charette | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Rendering models for the sole purpose of detecting changes between them
takes a significant amount of time on large project.
Instead of comparing the fake models rendered from the state generated by
applying `state_forwards` of all existing migrations against the current
model state generating model states from the current model classes and
comparing both would shave off a model rendering phase.
This was extracted from the meta ticket #22608 which tracks slow parts of
the migration framework.
An initial and dusty stab at this can be found here
https://github.com/django/django/compare/master...charettes:autodetector-
model-states
Note that this has a bit of overlap with #29898 because both optimizations
require a way to resolve relations efficiently from model states.
--
Ticket URL: <https://code.djangoproject.com/ticket/29899>
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/052.c8af03a7c83e21128910d391d48146a4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
