Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Fixed #22048 - Enhanced docs to cover nonexistent one-to-one relation…


Thanks EvilDMP for the suggestion.
  • Loading branch information...
commit ec08d62a20f55cfdfb9fbd21d8bc5627c54337c7 1 parent 60d2dde
@adamkal adamkal authored timgraham committed
9 docs/ref/models/fields.txt
@@ -1469,6 +1469,15 @@ your resulting ``User`` model will have the following attributes::
>>> hasattr(user, 'supervisor_of')
+A ``DoesNotExist`` exception is raised when accessing the reverse relationship
+if an entry in the related table doesn't exist. For example, if a user doesn't
+have a supervisor designated by ``MySpecialUser``::
+ >>> user.supervisor_of
+ Traceback (most recent call last):
+ ...
+ DoesNotExist: User matching query does not exist.
.. _onetoone-arguments:
Additionally, ``OneToOneField`` accepts all of the extra arguments
15 docs/topics/db/examples/one_to_one.txt
@@ -61,10 +61,17 @@ A Place can access its restaurant, if available::
p2 doesn't have an associated restaurant::
- >>>
- Traceback (most recent call last):
- ...
- DoesNotExist: Restaurant matching query does not exist.
+ >>> from django.core.exceptions import ObjectDoesNotExist
+ >>> try:
+ >>>
+ >>> except ObjectDoesNotExist:
+ >>> print("There is no restaurant here.")
+ There is no restaurant here.
+You can also use ``hasattr`` to avoid the need for exception catching::
+ >>> hasattr(p2, 'restaurant')
+ False
Set the place using assignment notation. Because place is the primary key on
Restaurant, the save will create a new restaurant::
Please sign in to comment.
Something went wrong with that request. Please try again.