Malcolm Tredinnick wrote: > > The consistent design idea at work here is that a manager provides those > methods that return a Queryset object. That is why we have .all() in the > first place: it provides a way to convert from a manager object to a > Queryset without applying any filters or restrictions at all to the > default.
I guessed that might have been the case, but became less sure when I saw that Manager implementes iterator() (which does not return a QuerySet). It seemed natural to me to support __iter__ delegating to iterator(), but from what you say, I guess the latter is an exception that doesn't set a precedent :) Cheers, Andrew. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
