Thanks for the input! So, I'm assuming by "easiest case" you mean just
calling LEFT OUTER JOINs. That's Rails behavior and then it deals with it
in Ruby. I'm not too familiar with SQLAlchemy, but it looks like that's
what they're doing in their EagerLoader as well.
The only way I can think of o
It isn't *an* extra SQL query that I'm worried about. It's that it's going
to be about 2,000 extra SQL queries in a loop. If it were just constructing
a page with one item and then its related items, that's not a problem to do
two queries, but when you're looping over 2,000 items and running an
2 matches
Mail list logo
