#24543: Add checks / command options for "migrations not applied" and
"migrations
needed"
-----------------------------+--------------------------------------
Reporter: blueyed | Owner:
Type: New feature | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------+--------------------------------------
Comment (by MarkusH):
When you need to roll-back during a deployment you have already lost, from
my point of view.
I agree with Tim that calling `migrate` as part of the deployment process
is the best approach, given its noop behavior if nothing needs to be
migrated. Furthermore, you can't reply on `MAX(id)`. If you roll-back a
migration the item is removed from the table and e.g. Postgres doesn't
reset the sequence.
As an aside for the `makemigrations` idea: have a look at #24484.
--
Ticket URL: <https://code.djangoproject.com/ticket/24543#comment:6>
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/065.9ebd584a41d690c320c17a4a7e082fab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
