#25390: Add support to specify a start migration in squashmigrations
-------------------------------------+-------------------------------------
Reporter: MarkusH | Owner: MarkusH
Type: New feature | Status: assigned
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: 1.9 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by timgraham:
Old description:
> The `squashmigrations` command currently only supports squashing all
> migrations from 0001 to a given input. If a migration in between uses
> `RunPython` or `RunSQL` the current `squashmigrations` behavior is
> infeasible due to restrictions from those to operations.
>
> `squashmigrations` should provide a way to define the first migration
> from which on the migrations are squashed up to the one given.
New description:
The `squashmigrations` command currently only supports squashing all
migrations from 0001 to a given input. If a migration in between uses
`RunPython` or `RunSQL` the current `squashmigrations` behavior is
infeasible due to restrictions from those two operations.
`squashmigrations` should provide a way to define the first migration from
which on the migrations are squashed up to the one given.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25390#comment:4>
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.4884c1ecaa615e8d1689a6b0d58ee1d8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
