#28785: Tracking migrations
-------------------------------+------------------------------------
Reporter: Ramez Kabbani | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Changes (by Tomer Chachamu):
* type: Uncategorized => New feature
* stage: Unreviewed => Accepted
Comment:
Agreed that a warning or system check for this situation would be nice.
However, the docs currently suggest a way to turn a squashed migration
into a normal migration, and it looks like any database that has had this
done will then fail the system check. So, we would need:
* A way to turn squashed migrations into normal migrations in the future
that does not cause the system check to fail,
* A solution for old databases to "reset" the system check, or we can just
recommend people add it to `SILENCED_SYSTEM_CHECKS` (which would be a bit
of a shame)
At the least, there might be a good place in the documentation to add a
warning that migration files should not be removed.
--
Ticket URL: <https://code.djangoproject.com/ticket/28785#comment:1>
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/070.98fef71e91134425fba3b6ac180aad94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
