#25250: Better Indication of Squash Migration State in showmigrations
-----------------------------+--------------------
Reporter: mlavin | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------
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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25250>
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/049.68859dd1b09a200e67a2d968adaf46f5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
