  
  **New in Django development version** 
  
  When you're only dealing with simple many-to-many relationships such as
  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. 
  
  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
 
</s> remove 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.
 </s> add 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. </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 <ref-manytomany>` for details.`
 </s> add <ref-manytomany>` for details. </s> remove reference <ref-foreignkey>` for details.`
 </s> add reference <ref-foreignkey>` for details.
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.
  
  **New in Django development version** 
  
  When you're only dealing with simple many-to-many relationships such as
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.
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.
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.
  
  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
keep keep keep keep 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