#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 |
-------------------------------------+-------------------------------------
Comment (by jaap3):
Yes, it seems to be a duplicate. I think I got confused after reading the
comments and the patches of the other ticket.
I've expended my testcases to include the proxy of proxy case, and will
attach it to the other bug. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/17140#comment:4>
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.
