#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
-------------------------------------+-------------------------------------
Changes (by erikr):
* stage: Unreviewed => Accepted
Comment:
Yes, this would be great. I ran into this just yesterday, and indeed
answered no because I just wasn't sure enough. I'm not sure whether
automatic deletion if there are no other objects is good - somehow it
seems to me that migrate should not automatically delete such data even if
it seems harmless.
--
Ticket URL: <https://code.djangoproject.com/ticket/24546#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 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/067.3975c4866e30f836d7f4177aab58adc4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
