We've always had a __len__ helper in the queryset, but it had side effects - it caused a query.
To fix that I implemented a cached queryset (ala django) but thats less than ideal also see: #365 as memory usage could be huge.
So the plan is to flip the default in 0.9 and don't provide a __len__ by default.
- Need to support
no_cache in the ne default (just return self) and educate users in the docs.
We've always had a
__len__helper in the queryset, but it had side effects - it caused a query.To fix that I implemented a cached queryset (ala django) but thats less than ideal also see: #365 as memory usage could be huge.
So the plan is to flip the default in 0.9 and don't provide a
__len__by default.no_cachein the ne default (just return self) and educate users in the docs.