On 4/4/07, Rob Hudson <[EMAIL PROTECTED]> wrote: > What would be more efficient would be if I could get all responses for a > particular user, then pluck the particular variables out of that data > set as/when I need them. 1 SQL call. Is that possible? Are there > memory tradeoffs? There could be potentially on the order of 100 > responses per user and each of those is a Response object. Is there a > way to estimate memory footprint for that? Is this even worth the > effort -- the individual queries are about .001s, and in total about > 0.065s for the particular page I'm looking at.
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. But keep in mind that this isn't always the best solution; some databases actually prefer getting lots of small queries to getting one or two really complex ones (e.g., MySQL is optimized for "lots of small queries", while Postgres tends to do better with one complex query). You'll definitely want to do some profiling to find out which option performs better for your database. [1] http://www.djangoproject.com/documentation/db-api/#select-related -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
