#27844: Add a management command to run the optimizer on a single migration
-----------------------------------------------+--------------------------
Reporter: Raphael Gaschignard | Owner: nobody
Type: New feature | Status: assigned
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------------+--------------------------
Because the migration optimizer still has a bit of trouble with reducing
operations, you often want to edit squashed migrations and re-run it
through the optimizer.
The attached patch contains an implementation of a management command,
{{{optimizemigration}}}, that will help speed up this process.
{{{optimizemigration app_name migration_name}}} reads a single migration,
pass it through the optimizer, and then rewrite the result to disk. Unlike
{{{squashmigrations}}}, this ignores things like the squashed-ness of the
migration.
--
Ticket URL: <https://code.djangoproject.com/ticket/27844>
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/047.cf21e7b7b08368d976e1d639ac94d66e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
