pub/mongoengine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

QuerySet count vs len #937

Browse Source 
Current documentation does not consider performance issues in using len instead of count.
https://github.com/MongoEngine/mongoengine/issues/937
This commit is contained in:
marcoskv 2015-07-26 22:41:24 +02:00
parent f8890ca841
commit a70ef5594d
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/guide/querying.rst
View File

@ -347,6 +347,8 @@ way of achieving this::
num_users = len(User.objects) num_users = len(User.objects)
Even if len() is the Pythonic way of counting results, keep in mind that if you concerned about performance, :meth:`~mongoengine.queryset.QuerySet.count` is the way to go since it only execute a server side count query, while len() retrieves the results, places them in cache, and finally counts them. If we compare the performance of the two operations, len() is much slower than :meth:`~mongoengine.queryset.QuerySet.count`.
Further aggregation Further aggregation
------------------- -------------------
You may sum over the values of a specific field on documents using You may sum over the values of a specific field on documents using