#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 timgraham):
Markus, can you elaborate on the data loss concerns? I guess it's about
the possibility of delete cascades which is why interactive prompts were
originally added in #12339. I don't think there's much value in completing
this ticket if it isn't a public API. I'd think documentation that
explains the data-loss considerations would do more to educate users than
keeping the function private would. If you have another idea on how to
address the use case in #24820 I'm open to alternatives.
--
Ticket URL: <https://code.djangoproject.com/ticket/24865#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.62777b0371015bffcfb67139d7fca271%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
