#26080: Missing field.on_delete
-------------------------------------+-------------------------------------
Reporter: srkunze | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
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):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
As far as I know `on_delete` is only applicable to `ForeignKey` and
`OneToOneField` (which inherits `OneToOneField` so why not check
`isinstance(field, ForeignKey)` instead of `field.is_relation`?
For what it's worth, I found this pattern in Django: `getattr(rel,
'on_delete', None) is CASCADE`.
I'm not convinced that `on_delete` must be a standard attribute of all
relational fields.
--
Ticket URL: <https://code.djangoproject.com/ticket/26080#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/065.a4c13f33f3f18a16b6127554800fc6ca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
