#12420: "OneToOneField doesn't allow assignment of None"
---------------------------------------------------+------------------------
Reporter: kbrownlees | Owner: andrewsk
Status: closed | Milestone: 1.2
Component: Database layer (models, ORM) | Version: SVN
Resolution: fixed | Keywords:
Stage: Ready for checkin | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by jkocherhans):
In case anyone wonders, I didn't backport this because the tests fail on
1.1.X. I'm guessing that the change to !OneToOneField that made this
possible on trunk isn't on that branch.
--
Ticket URL: <http://code.djangoproject.com/ticket/12420#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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
