Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #11931: Removed mention of nonexistent get_sql() method for arg…

…uments to limit_choices_to. Since the correct reference involves undocumented ORM internals, this simply removes the reference entirely in favor of publicly-documented use of Q objects.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11591 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
commit 4a2a0b0e21a7f6ae55d0bc70c8cabf047debc927 1 parent 0a7dc8d
James Bennett authored September 23, 2009
2  docs/ref/models/fields.txt
@@ -844,7 +844,7 @@ define the details of how the relation works.
844 844
     current date/time to be chosen.
845 845
 
846 846
     Instead of a dictionary this can also be a :class:`~django.db.models.Q`
847  
-    object (an object with a :meth:`get_sql` method) for more complex queries.
  847
+    object for more :ref:`complex queries <complex-lookups-with-q>`.
848 848
 
849 849
     ``limit_choices_to`` has no effect on the inline FormSets that are created
850 850
     to display related objects in the admin.
2  docs/topics/db/queries.txt
@@ -622,6 +622,8 @@ To avoid this problem, simply save the ``QuerySet`` and reuse it::
622 622
     >>> print [p.headline for p in queryset] # Evaluate the query set.
623 623
     >>> print [p.pub_date for p in queryset] # Re-use the cache from the evaluation.
624 624
 
  625
+.. _complex-lookups-with-q:
  626
+
625 627
 Complex lookups with Q objects
626 628
 ==============================
627 629
 

0 notes on commit 4a2a0b0

Please sign in to comment.
Something went wrong with that request. Please try again.