> As an aside, does this mean my Web2Py sessions will be reasonably large, > because competition entry rows on their own have a lot of baggage about > competition-section-category-sponsors and registered_by info?, ...or is > Web2Py smart enough to only call in that extra information if required? (I > find it hard to believe it is on-demand, since Web2Py would surely need to > launch another query just for these references, yes?) > > it's exactly as described. one query for each hoop of every row. Web2py is only smart enough to NOT do queries for each "linked" table unless you're requiring it's explicit "attributes"
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
