On 28/09/11 00:07, Johannes Dollinger wrote: > > Am 27.09.2011 um 05:18 schrieb Luke Plant: > >> 1) could be done on a per-query basis and >> 2) didn't require changes to the code that would use the QuerySet >> objects i.e. fully API compatible. > > I don't believe (2) is an important requirement. It may even be > counter-productive.
If you are trying to improve the performance of existing code, it's quite an important requirement. It's analogous to select_related - if you had to use different code in order to get the benefits from select_related it wouldn't be nearly so useful. Template authors shouldn't have to learn a new set of attributes in order to benefit from either of these performance related APIs. > For me, the ideal solution would allow to filter or annotate the > prefetched QuerySet – and thus, obj.relmanager.all() would be a bad > API to access the prefetched objects. I'd like to propose something > that works more like annotations: This is a much bigger feature, and introduces a whole bunch of changes and additions which I don't think are realistic until we've got basic functionality in place. Regards, Luke -- "I spilled spot remover on my dog. Now he's gone." (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- 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.
