Made a couple of cross-references in the model fields documentaiton consistent.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@10007 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
059765fa6c
commit
98710a5a28
|
@ -869,14 +869,14 @@ that control how the relationship functions.
|
||||||
|
|
||||||
Same as :attr:`ForeignKey.related_name`.
|
Same as :attr:`ForeignKey.related_name`.
|
||||||
|
|
||||||
.. attribute:: ManyToManyFields.limit_choices_to
|
.. attribute:: ManyToManyField.limit_choices_to
|
||||||
|
|
||||||
Same as :attr:`ForeignKey.limit_choices_to`.
|
Same as :attr:`ForeignKey.limit_choices_to`.
|
||||||
|
|
||||||
``limit_choices_to`` has no effect when used on a ``ManyToManyField`` with
|
``limit_choices_to`` has no effect when used on a ``ManyToManyField`` with
|
||||||
an intermediate table.
|
an intermediate table.
|
||||||
|
|
||||||
.. attribute:: ManyToManyFields.symmetrical
|
.. attribute:: ManyToManyField.symmetrical
|
||||||
|
|
||||||
Only used in the definition of ManyToManyFields on self. Consider the
|
Only used in the definition of ManyToManyFields on self. Consider the
|
||||||
following model::
|
following model::
|
||||||
|
@ -895,7 +895,7 @@ that control how the relationship functions.
|
||||||
add the descriptor for the reverse relationship, allowing
|
add the descriptor for the reverse relationship, allowing
|
||||||
:class:`ManyToManyField` relationships to be non-symmetrical.
|
:class:`ManyToManyField` relationships to be non-symmetrical.
|
||||||
|
|
||||||
.. attribute:: ManyToManyFields.through
|
.. attribute:: ManyToManyField.through
|
||||||
|
|
||||||
Django will automatically generate a table to manage many-to-many
|
Django will automatically generate a table to manage many-to-many
|
||||||
relationships. However, if you want to manually specify the intermediary
|
relationships. However, if you want to manually specify the intermediary
|
||||||
|
|
|
@ -381,7 +381,7 @@ 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
|
to govern the many-to-many relationship. You can then put extra fields on the
|
||||||
intermediate model. The intermediate model is associated with the
|
intermediate model. The intermediate model is associated with the
|
||||||
:class:`~django.db.models.ManyToManyField` using the
|
:class:`~django.db.models.ManyToManyField` using the
|
||||||
:attr:`through <ManyToManyFields.through>` argument to point to the model
|
:attr:`through <ManyToManyField.through>` argument to point to the model
|
||||||
that will act as an intermediary. For our musician example, the code would look
|
that will act as an intermediary. For our musician example, the code would look
|
||||||
something like this::
|
something like this::
|
||||||
|
|
||||||
|
@ -426,7 +426,7 @@ There are a few restrictions on the intermediate model:
|
||||||
|
|
||||||
* When defining a many-to-many relationship from a model to
|
* When defining a many-to-many relationship from a model to
|
||||||
itself, using an intermediary model, you *must* use
|
itself, using an intermediary model, you *must* use
|
||||||
:attr:`symmetrical=False <ManyToManyFields.symmetrical>` (see
|
:attr:`symmetrical=False <ManyToManyField.symmetrical>` (see
|
||||||
:ref:`the model field reference <manytomany-arguments>`).
|
:ref:`the model field reference <manytomany-arguments>`).
|
||||||
|
|
||||||
Now that you have set up your :class:`~django.db.models.ManyToManyField` to use
|
Now that you have set up your :class:`~django.db.models.ManyToManyField` to use
|
||||||
|
|
Loading…
Reference in New Issue