Opened 9 years ago
Last modified 9 years ago
#25390 closed New feature
Add support to specify a start migration in squashmigrations — at Version 4
| Reported by: | Markus Holtermann | Owned by: | Markus Holtermann |
|---|---|---|---|
| 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 (last modified by )
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.
Change History (4)
comment:1 by , 9 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Has patch: | set |
|---|---|
| Needs documentation: | unset |
| Needs tests: | unset |
comment:3 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:4 by , 9 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.
PR: https://github.com/django/django/pull/5277