#10227: OneToOne fields with null=True raise DoesNotExist exception on related
model
---------------------------------------------------+------------------------
Reporter: rvdrijst | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords: onetoone
related expection null
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by olau):
* cc: [email protected] (added)
Comment:
I've run into the case where every Shop has a Place, but some places don't
have a shop. So I think we need to model it with a separate parameter,
e.g. related_null=True. That would also be backwards-compatible. Aren't
there four cases? So we need two bits to describe them:
{{{
one to one
zero or one to one
one to zero or one
zero or one to zero or one
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/10227#comment:7>
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.
