I'd just like to chime in to say this should definitely be part of core - it's a common requirement, and whilst it could be a third party app, it certainly feels much more at home in core.
On Sep 27, 1:13 pm, Luke Plant <l.plant...@cantab.net> wrote: > For me, QuerySet is at a level of abstraction where I don't think it > guarantees a single query. We have quite a bit of precedent here I think: I also agree on this - many ORMs give the option to fetch objects using a separate select (I'm thinking for example hibernates "FetchMode.SELECT"). I think if you explicitly use this then you probably need to understand what it does like anything else. I've only had a brief look at the patch, but no doubt even if it needs some polish it'll be a good start! -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
