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
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
Fellow Djangonauts,
Here at my work[1] we've built a number of web-based educational
websites in Django now. I'm analyzing the number of SQL calls and am
realizing that the number is higher than I'd like.
My main question is around whether or not I can do a bulk query to get
most of the
3 matches
Mail list logo
