#24546: Deletion of stale content types during migrate should show cascade
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: master
commands) |
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
-------------------------------------+-------------------------------------
Comment (by carljm):
I _wish_ content types were an implementation detail (or didn't exist at
all), but unfortunately I don't think that's the case. They are a core
part of the GenericForeignKey, which is very much a user-visible feature.
And the ContentType model itself is documented as a user-visible feature,
as well, so it would be entirely reasonable for people to have cascading
FKs pointing to ContentType, and that would be within public documented
API.
--
Ticket URL: <https://code.djangoproject.com/ticket/24546#comment:3>
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/067.84a9c29e240842f09d368b5d7fe831ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
