> Why don't you just generate lists and dictionaries in the view and send
> those to your templates instead of data objects?
I like having access to the models attributes, such as
get_absolute_url, we use things like this quite a bit in our templates
> 1. It'd be pretty easy to write a template tag -- say, {% cache %}{%
endcache %} -- which caches all the nodes within itself; this way you
can isolate parts of the template which hit the DB, and cache those
results without having to cache the entire rendered template.
I may look into this, but I'd still prefer something as to where I
could block it in the template. It'd just be easier to find the loose
queries/etc if I could do that.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
