#25988: Change django.db.models.deletion.CASCADE to
django.db.models.deletion.PROTECT while creating migrations
--------------------------------------+--------------------
Reporter: sagrawal-idrc | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
By default, on deletion, the changes shouldn't be cascaded, but protected.
Results in loss of data if the migrations generated are not checked
carefully.
--
Ticket URL: <https://code.djangoproject.com/ticket/25988>
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/056.a90c73305bacec12dd89a8007f09b4a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
