Opened 9 years ago
Last modified 9 years ago
#25390 closed New feature
Add support to specify a start migration in squashmigrations — at Initial Version
| Reported by: | Markus Holtermann | Owned by: | |
|---|---|---|---|
| Component: | Core (Management commands) | Version: | dev |
| Severity: | Normal | Keywords: | 1.9 |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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.
Note:
See TracTickets
for help on using tickets.