#14043: Incorrect and/or confusing behaviour with nullable OneToOneField
--------------------------------------------------------+-------------------
Reporter: theevilgeek | Owner:
Status: new | Milestone: 1.3
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
OneToOneField, cascading delete, nullable
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 1
Patch needs improvement: 1 |
--------------------------------------------------------+-------------------
Changes (by russellm):
* needs_better_patch: 0 => 1
* needs_tests: 0 => 1
* stage: Ready for checkin => Accepted
Comment:
The provided test case doesn't validate the problem described. If you
revert the change to related.py, the test case doesn't fail.
--
Ticket URL: <http://code.djangoproject.com/ticket/14043#comment:9>
Django <http://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.
