#36303: Add ghost migrations warning to runserver
---------------------------------------+-----------------------------
Reporter: Jacob Walls | Owner: Jacob Walls
Type: New feature | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
---------------------------------------+-----------------------------
On the [https://forum.djangoproject.com/t/check-for-ghost-migrations-
opposite-of-you-have-n-unapplied-migration-s/38657 forum], several folks
indicated interest in supplementing the runserver warning about missing
migrations with a warning for "ghost" migrations: migrations recorded on
the database but not present on disk, presumably as a consequence of
switching away from a feature branch under development.
I suggested wording along the lines of:
{{{
The following migrations are recorded as applied but no longer exist in
your project:
…
Your project may not work correctly if they are reversible and are
intended to be reversed.
To reverse the migrations, recover them (e.g. by switching branches) and
run:
“manage.py migrate <app_name> <last_migration_on_disk>”
If you are certain the migrations do not need to be reversed, run:
“manage.py migrate <app_name> --prune” to remove references to them.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36303>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070196107b1a89-a3a65a53-a654-45bc-8bcb-28314dc523a7-000000%40eu-central-1.amazonses.com.
