Is there a reason that QuerySet methods like order_by() or filter() don't simply pass on an appropriately modified version of their own cache to the new QuerySet?
I was just recently optimizing database usage in a django app and found myself managing these things myself (sorted(qs) instead of qs.order_by(), filter(filterer, qs) instead of qs.filter()) because I didn't want the database to get hit again when modifying already-used querysets. I didn't want to add a ticket if this was a conscious decision - this would be a parallel implementation on top of the DB, and there's something to be said for uniformity there. queryset-refactor is a pretty major refactor, and I didn't look into it deep enough to be sure, but it didn't look like that branch was doing this either. Am I mistaken? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
