On Jun 18, 4:46 pm, saxon75 <[EMAIL PROTECTED]> wrote:
> Thanks for your response!
>
> I actually do something similar to what you describe when I'm
> displaying a single node and it works great. The problem I'm having
> is when I want to grab many nodes and display all of them on the same
> page. So, I suppose what I could do is either iterate over the
> QuerySet in the view function, calling render_to_string in each
> iteration and then concatenating the rendered strings and passing that
> to an HttpResponse object, or iterate over the QuerySet in the
> template and have a custom template tag render each node separately.
> I think I like the latter option better.
Yep...the templatetag is definitely cleaner and it is reusable. Pre-
iterating over the QuerySet is less efficient in cases where you are
not going to be displaying all items of the QuerySet (for example,
when paginating.)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
