James Bennett wrote: > The 'select_related' method[1] may be what you're looking for; it > selects related objects up-front in the same query, so that later > access doesn't go back and hit the DB again.
Yes, I'm doing this where it makes sense. What I'm looking for is whether there is a way to say these types of things without making another database call: * Of this list of Response objects which I already have, give me a list where this filter condition is true. * Of this list of Content objects, remove those where this filter condition is true. Would iterating over the list and checking each object be faster than simply making another db call? Maybe I'm making more of an efficiency issue out of this than it really is, but I thought I'd at least investigate ways to optimize what we have. Thanks, Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
