#21640: ForeignKey.on_delete doesn't call models save function.
-------------------------------------+-------------------------------------
Reporter: traverse.da@… | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.5
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
Yeah, I was worried it would be something like that.
I hadn't considered rewriting SET_NULL, and it seems like I might be able
to get it to work.
It would be nice if there was some easy way to run real code when a
foriegnkey gets deleted, but for my purposes rewriting SET_NULL should do.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/21640#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/079.0fffe0db9c998ebcced283b0ee3ac0e9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
