Opened 4 years ago

Closed 4 years ago

#25390 closed New feature (fixed)

Allow specifying a start migration in squashmigrations

Reported by: Markus Holtermann Owned by: Markus Holtermann
Component: Core (Management commands) Version: master
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 Tim Graham)

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 (6)

comment:1 Changed 4 years ago by Markus Holtermann

Owner: set to Markus Holtermann
Status: newassigned

comment:2 Changed 4 years ago by Markus Holtermann

Has patch: set
Needs documentation: unset
Needs tests: unset

comment:3 Changed 4 years ago by Tim Graham

Triage Stage: UnreviewedAccepted

comment:4 Changed 4 years ago by Tim Graham

Description: modified (diff)

comment:5 Changed 4 years ago by Tim Graham

Summary: Add support to specify a start migration in squashmigrationsAllow specifying a start migration in squashmigrations
Triage Stage: AcceptedReady for checkin

comment:6 Changed 4 years ago by Markus Holtermann <info@…>

Resolution: fixed
Status: assignedclosed

In 43f2eb7e:

Fixed #25390 -- Allowed specifying a start migration in squashmigrations

Thanks Tim Graham for the review.

Note: See TracTickets for help on using tickets.
Back to Top