      ed = EntryDetail.objects.get(id=2)
      ed.entry # Returns the related Entry object.
  
  The difference comes in "reverse" queries. The related model in a one-to-one
  relationship also has access to a ``Manager`` object, but that ``Manager``
  represents a single object, rather than a collection of objects::
  
      e = Entry.objects.get(id=2)
      e.entrydetail # returns the related EntryDetail object
  
  If no object has been assigned to this relationship, Django will raise
 
</s> remove define a ``OneToOneField`` on your model, instances of that model will have
access to the related object via a simple attribute of the model.
 </s> add define a :class:`~django.db.models.OneToOneField` on your model, instances of
that model will have access to the related object via a simple attribute of the
model. </s> remove object with a many-to-one relationship to itself) and :ref:`relationsips to
 </s> add object with a many-to-one relationship to itself) and :ref:`relationships to </s> remove <ref-manytomany>` for details.`
 </s> add <ref-manytomany>` for details. </s> remove of `methods automatically given to each model <model-instance-methods>`. You can
override most of these -- see `overriding predefined model methods`_, below --
but there are a couple that you'll almost always want to define:
 </s> add of :ref:`methods automatically given to each model <model-instance-methods>`.
You can override most of these -- see `overriding predefined model methods`_,
below -- but there are a couple that you'll almost always want to define: </s> remove reference <ref-foreignkey>` for details.`
 </s> add reference <ref-foreignkey>` for details.
relationship also has access to a :class:`~django.db.models.Manager` object, but
that :class:`~django.db.models.Manager` represents a single object, rather than
a collection of objects::
      ed = EntryDetail.objects.get(id=2)
      ed.entry # Returns the related Entry object.
  
  The difference comes in "reverse" queries. The related model in a one-to-one
relationship also has access to a :class:`~django.db.models.Manager` object, but
that :class:`~django.db.models.Manager` represents a single object, rather than
a collection of objects::
relationship also has access to a :class:`~django.db.models.Manager` object, but
that :class:`~django.db.models.Manager` represents a single object, rather than
a collection of objects::
  
      e = Entry.objects.get(id=2)
      e.entrydetail # returns the related EntryDetail object
  
  If no object has been assigned to this relationship, Django will raise
keep keep keep keep replace replace keep keep keep keep keep
 Fixed a handful of typo/markup problems in the docs. Patch from Daniel Roseman.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@8540 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/topics/db/models.txt