#17140: Unexpected behaviour with on_delete handlers and proxy models
(IntegrityError)
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.3
(models, ORM) | Resolution: duplicate
Severity: Normal | Triage Stage: Accepted
Keywords: ForeignKey | Needs documentation: 0
on_delete proxy model | Patch needs improvement: 0
IntegrityError CASCADE SET_NULL | UI/UX: 0
Has patch: 0 |
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by carljm):
* status: new => closed
* resolution: => duplicate
Comment:
I'm not sure I see how this is the reverse of #16128. If I'm reading that
one right, the failure is in the exact same case: FK pointing to proxy
model, real parent of proxy deleted. I think this is a duplicate of that
ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/17140#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
