diff options
| -rw-r--r-- | docs/ref/models/fields.txt | 2 | ||||
| -rw-r--r-- | docs/topics/db/queries.txt | 2 |
2 files changed, 3 insertions, 1 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 177df12862..0cb5be4b92 100644 --- a/docs/ref/models/fields.txt +++ b/docs/ref/models/fields.txt @@ -844,7 +844,7 @@ define the details of how the relation works. current date/time to be chosen. Instead of a dictionary this can also be a :class:`~django.db.models.Q` - object (an object with a :meth:`get_sql` method) for more complex queries. + object for more :ref:`complex queries <complex-lookups-with-q>`. ``limit_choices_to`` has no effect on the inline FormSets that are created to display related objects in the admin. diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index 5e353b2ec3..968ea7fbc8 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -622,6 +622,8 @@ To avoid this problem, simply save the ``QuerySet`` and reuse it:: >>> print [p.headline for p in queryset] # Evaluate the query set. >>> print [p.pub_date for p in queryset] # Re-use the cache from the evaluation. +.. _complex-lookups-with-q: + Complex lookups with Q objects ============================== |