From de9942a6673cfbe442abdfabc1e8f7c0a652ef5b Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Tue, 28 Feb 2012 19:34:04 +0000 Subject: Fixed #17668 - prefetch_related does not work in in_bulk Thanks to gurets for the report, and akaariai for the initial patch. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17600 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/ref/models/querysets.txt | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/ref') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 4d6b9bc533..13504f41cf 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -871,6 +871,9 @@ could be generated, which, depending on the database, might have performance problems of its own when it comes to parsing or executing the SQL query. Always profile for your use case! +Note that if you use ``iterator()`` to run the query, ``prefetch_related()`` +calls will be ignored since these two optimizations do not make sense together. + extra ~~~~~ @@ -1430,6 +1433,9 @@ performance and a significant reduction in memory. Note that using ``iterator()`` on a ``QuerySet`` which has already been evaluated will force it to evaluate again, repeating the query. +Also, use of ``iterator()`` causes previous ``prefetch_related()`` calls to be +ignored since these two optimizations do not make sense together. + latest ~~~~~~ -- cgit v1.3