#24109: Provide a way to mark a migration operation as elidable when squashing
-----------------------------+--------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
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
-----------------------------+--------------------------------------
Comment (by shaib):
While this appears to be a generally good idea, I think a better solution
for the use-case would be a specific data-move operation, if we can come
up with one that is general enough. Usually, the data-migration is needed
because old-field and new-field are not on the same model (incl. moving
from FK to M2M) -- or because some explicit transformation is required
(e.g. turning some field from string to number). These, I suspect, can be
collected into an operation that the optimizer and the executor can
understand, and perhaps could even be auto-detected in some way.
--
Ticket URL: <https://code.djangoproject.com/ticket/24109#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/064.45970c8a00404eaeb62eb00e94f6bedd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
