#24865: Add a feature to programmatically remove stale content types
--------------------------------------+------------------------------------
Reporter: Protosac | Owner:
Type: New feature | Status: new
Component: contrib.contenttypes | Version: master
Severity: Normal | Resolution:
Keywords: stale contenttypes | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by amosonn):
I think that the other side of not removing stale content types for fear
of data loss is leaving stale `GenericForeignKey`s, which will break when
accessed (see #25931). Hard to say which is worse.
I think perhaps adding a switch to migrate is better:
`--remove_stale_contenttypes` or `--keep_stale_contenttypes`, and if none
are present then default to current interactive behaviour.
--
Ticket URL: <https://code.djangoproject.com/ticket/24865#comment:16>
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/066.6e5b779cdf6b58d24c179730019660d0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
