#25988: Change django.db.models.deletion.CASCADE to
django.db.models.deletion.PROTECT while creating migrations
-------------------------------------+-------------------------------------
Reporter: sagrawal-idrc | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Migrations | Version: 1.9
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
Thanks for the suggestion, but it's obsolete because Django 1.9
[https://docs.djangoproject.com/en/dev/releases/1.9/#foreignkey-and-
onetoonefield-on-delete-argument deprecates the default value] for
`on_delete` so that in Django 2.0, the developer must specify a value.
--
Ticket URL: <https://code.djangoproject.com/ticket/25988#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 [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/071.d85431ca957878254385ffa06f7d7de1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
