Calling limit() on a queryset does not actually limit results on server side call

[andrewbelu]

I am trying to limit the results of a query and feed the queryset to a Django template. When I try to perform the following:

records = Record.objects(query).limit(10)

And send it to a Django (v1.7) table template, this results in more than 10 records appearing in my table (71 to be exact).

Note that if I call records.count() after the limit(), it returns 71. len(records) returns 10 however.

I am using mongoengine 0.9 and pymongo 2.8.

Also note, if I cast records to a list it works fine, but I lose some of the pagination/queryset capabilities I would want.

[DavidBord]

For the count you should add a flag with_limit_and_skip=True
For the rest, could you please provide a failing test case?

[andrewbelu]

Where do you want me to add a test case?

Note, I believe this is related to hmarr#166

[MRigal]

ping @andrewbelu

[andrewbelu]

My apologies for the long wait, I forgot about this issue entirely.

Created pull request: #981

[MRigal]

Thanks @andrewbelu

[elephanter]

Hello. I'm look into the problem and found that failed unit test used __getitem__ access to queryset

for i in xrange(0, 10):
    posts[i]

inside queryset in that case mongoengine call pymongo.cursor also with __getitem__ method.
now looking in pymongo documentation we will see that:

db.test.find()[50]
An IndexError will be raised if the index is negative or greater than the amount of documents in this cursor. Any limit previously applied to this cursor will be ignored.

That behavior is not a bug.