Refs #8319 -- Added documentation note on the limitations of limit_choices_to.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8365 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2008-08-15 07:55:41 +00:00
parent 1691c22821
commit 7eb44e32dc
1 changed files with 5 additions and 1 deletions

View File

@ -869,7 +869,8 @@ relationship should work. All are optional:
(an object with a ``get_sql()`` method) for more complex (an object with a ``get_sql()`` method) for more complex
queries. queries.
Not compatible with ``edit_inline``. ``limit_choices_to`` has no effect the inline FormSets that
are created to display related objects in the admin.
``related_name`` The name to use for the relation from the related ``related_name`` The name to use for the relation from the related
object back to this one. See the object back to this one. See the
@ -948,6 +949,9 @@ the relationship should work. All are optional:
``related_name`` See the description under ``ForeignKey`` above. ``related_name`` See the description under ``ForeignKey`` above.
``limit_choices_to`` See the description under ``ForeignKey`` above. ``limit_choices_to`` See the description under ``ForeignKey`` above.
``limit_choices_to`` has no effect when used on a
``ManyToManyField`` with an intermediate table.
``symmetrical`` Only used in the definition of ManyToManyFields on self. ``symmetrical`` Only used in the definition of ManyToManyFields on self.
Consider the following model:: Consider the following model::