Max Battcher wrote:
> So, I'm not sure if such an improvement is really necessary, again as
> the biggest case I see _for_ it being template performance, and I'm
> wondering if there might be a better way to optimize that single edge
> instead (ie, is it worth it to have some caching added to
> django.template's resolve_variable() for QuerySets?).
Yes, the only place this is really a concern is templates, and in these
the biggest place where you want caching is for foreign key
relationships such as:
Article by: {% article.reporter.first_name %} {%
article.reporter.surname %}
It looks like there is already caching in place for this, though I
haven't checked it actually works. So I think you are right here that
the caching is unnecessary.
Luke
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
