Skip to content
Browse files

Added warning about the performance of large IN clauses in prefetch_r…

…elated docs

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 648adcd commit e954a03871cdc1c155ba7a3f3000dcf75998d9f4 @spookylukey spookylukey committed
Showing with 6 additions and 0 deletions.
  1. +6 −0 docs/ref/models/querysets.txt
6 docs/ref/models/querysets.txt
@@ -821,6 +821,12 @@ referenced is needed, rather than one query for all the items. There could be
additional queries on the ``ContentType`` table if the relevant rows have not
already been fetched.
+``prefetch_related`` in most cases will be implemented using a SQL query that
+uses the 'IN' operator. This means that for a large QuerySet a large 'IN' clause
+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!

0 comments on commit e954a03

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