Opened 9 years ago

Closed 3 years ago

#25250 closed Cleanup/optimization (fixed)

Better Indication of Squash Migration State in showmigrations

Reported by: Mark Lavin Owned by: Jacob Walls
Component: Migrations Version: dev
Severity: Normal Keywords:
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

In the discussion of #25231 (https://github.com/django/django/pull/5112) it became clear that there was a disconnect between the current output of showmigrations and the actual recorded applied state of squashed migrations.

Currently if all of the replaced/original migrations have been run, showmigrations will output that the related squashed migration has been applied with an [X] in the output even if that has not yet been recorded by the migration recorder. However, it is currently a requirement that migrate be run to record this applied state for the squashed migration before the original migrations are removed. If a deployment process is looking for an empty [ ] to know to run the migration then this may trip it up.

This case is to consider an output for showmigrations which can indicate that this migration has only been "soft" applied, that is applied but not recorded yet.

Changes to the planner for such an output may also impact #24900.

Change History (6)

comment:1 by Carl Meyer, 9 years ago

Triage Stage: UnreviewedAccepted

comment:2 by Jacob Walls, 3 years ago

Owner: changed from nobody to Jacob Walls
Status: newassigned

comment:3 by Jacob Walls, 3 years ago

Has patch: set

comment:4 by Mariusz Felisiak, 3 years ago

Type: New featureCleanup/optimization

comment:5 by Mariusz Felisiak, 3 years ago

Triage Stage: AcceptedReady for checkin

comment:6 by Mariusz Felisiak <felisiak.mariusz@…>, 3 years ago

Resolution: fixed
Status: assignedclosed

In 2dfc106:

Fixed #25250 -- Clarified partially recorded state of squashed migrations in showmigrations --list.

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