> "Normally" (which might well mean "hopefully") it shouldn't matter > whether you're getting back an iterator or a list (which is still > iterable) at that point in the code. I could imagine or construct code > that behaves differently in the two cases, but do you have a real-life > case where the change in type is causing a problem?
After being remembered that placing code before/after evaluation is the point of the matter it was quite easy to fix. Here is what I was trying to do: http://dpaste.com/114134/ The queryset is used to populate a form and a subset of the field is needed at a other place in the template. My intention was to: a) find the first 20 results b) know if result amount exceeds the limit I guess there's much room for optimizations ;) --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
