#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 jacob):
* needs_better_patch: => 0
* stage: Unreviewed => Design decision needed
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not entirely sure what the correct behavior here ought to be: the fact
that `Shop.place` may be null doesn't necessarily imply that `Place.shop`
also may be null. That is, it may be correct for some situations that a
`Shop` may not have a `Place` but that `Place` always has an associated
`Shop`.
--
Ticket URL: <http://code.djangoproject.com/ticket/10227#comment:2>
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
-~----------~----~----~----~------~----~------~--~---
