From 7eb44e32dc451f4ba3cad780f7e68d148f8ee661 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Fri, 15 Aug 2008 07:55:41 +0000 Subject: [PATCH] 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 --- docs/model-api.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/model-api.txt b/docs/model-api.txt index 6dee963621..fc0299374d 100644 --- a/docs/model-api.txt +++ b/docs/model-api.txt @@ -869,7 +869,8 @@ relationship should work. All are optional: (an object with a ``get_sql()`` method) for more complex 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 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. ``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. Consider the following model::