#24865: Add a feature to programmatically remove stale content types
--------------------------------------+------------------------------------
Reporter: Protosac | Owner: nobody
Type: New feature | Status: new
Component: contrib.contenttypes | Version: master
Severity: Normal | Resolution:
Keywords: stale contenttypes | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by MarkusH):
Tim, neither patch is guaranteed to work when a user has not applied all
`contenttypes` migrations, as the model used inside the
`update_contenttypes` is from the global apps, not from the latest applied
migration state (see #24100 for that).
Anyway, I'm ok with making it a public API if we put a `.. warning::` box
around the docs and state the potential data loss due to cascading.
--
Ticket URL: <https://code.djangoproject.com/ticket/24865#comment:7>
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.6c0eff0d0e8b0c77b6ab4e03851e005d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
