  relationship between two models. 
  
  For example, consider the case of an application tracking the musical groups
  which musicians belong to. There is a many-to-many relationship between a person
  and the groups of which they are a member, so you could use a ManyToManyField
  to represent this relationship. However, there is a lot of detail about the
  membership that you might want to collect, such as the date at which the person
  joined the group.
  
  For these situations, Django allows you to specify the model that will be used
  to govern the many-to-many relationship. You can then put extra fields on the
  intermediate model. The intermediate model is associated with the
  ``ManyToManyField`` using the ``through`` argument to point to the model
 
</s> remove mixing and matching pizzas and toppings, a standard ``ManyToManyField``
is all you need. However, sometimes you may need to associate data with the
relationship between two models. 
 </s> add mixing and matching pizzas and toppings, a standard :class:`~django.db.models.ManyToManyField` is all you need. However, sometimes
you may need to associate data with the relationship between two models. </s> remove ``ManyToManyField`` using the ``through`` argument to point to the model
 </s> add :class:`~django.db.models.ManyToManyField` using the 
:attr:`through <ManyToManyFields.through>` argument to point to the model </s> remove       ``symmetrical=False`` (see the documentation for
      ``ManyToManyField`` above).
 </s> add       :attr:`symmetrical=False <ManyToManyFields.symmetrical>` (see 
      :ref:`the model field reference <manytomany-arguments>`). </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 reference <ref-foreignkey>` for details.`
 </s> add reference <ref-foreignkey>` for details.
and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group.
  relationship between two models. 
  
  For example, consider the case of an application tracking the musical groups
  which musicians belong to. There is a many-to-many relationship between a person
and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group.
and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group.
and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group.
and the groups of which they are a member, so you could use a
:class:`~django.db.models.ManyToManyField` to represent this relationship.
However, there is a lot of detail about the membership that you might want to 
collect, such as the date at which the person joined the group.
  
  For these situations, Django allows you to specify the model that will be used
  to govern the many-to-many relationship. You can then put extra fields on the
  intermediate model. The intermediate model is associated with the
  ``ManyToManyField`` using the ``through`` argument to point to the model
keep keep keep keep replace replace 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