On 1/9/06, John Siracusa <[EMAIL PROTECTED]> wrote: > On 1/9/06, Scott Karns <[EMAIL PROTECTED]> wrote: >> OK, that certainly works. Perhaps not exactly as I had expected, but it >> works. I guess I was approaching it as though the query was a multi-table >> inner join with the iterator returning a single row of the query result >> containing all columns of all tables involved.
Just to clarify what RDBO's Manager does do, it always returns one object from the primary table per iteration. That object may or may not have N sub-objects hanging off of it M levels deep. And... On 1/9/06, John Siracusa <[EMAIL PROTECTED]> wrote: > Also note that you could remove all of the "require_objects" args in > the get_persons_iterator() call and leave the loop code as-is. The > difference would be that many more queries would be run, of course. > With the require_objects arguments as shown, all information should be > retrieved in a single query. But semantically, that's an optimization > from the perspective of the loop code. That's actually not true in this particular case since the require_objects param also acts as a way to filter out any person who doesn't have any courses (and therefore isn't a teacher). So that call would actually mean something different if require_objects was removed. -John ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
