[sqlalchemy] Re: eagerload_all issue

2007-09-11 Thread Michael Bayer
On Sep 11, 2007, at 10:28 AM, Jean-Philippe Dutreve wrote: The name is on account, not on entry. Transactions and all must be loaded in one shot starting from a single account: account (e.g. id=7) == all its entries === one Transaction for each entry == all entries of each

[sqlalchemy] Re: eagerload_all issue

2007-09-11 Thread Jean-Philippe Dutreve
Ive uploaded the script eagerload_all.py that reproduce the issue. Hope it helps you. On 11 sep, 16:43, Michael Bayer [EMAIL PROTECTED] wrote: On Sep 11, 2007, at 10:28 AM, Jean-Philippe Dutreve wrote: The name is on account, not on entry. Transactions and all must be loaded in one shot

[sqlalchemy] Re: eagerload_all issue

2007-09-11 Thread Jean-Philippe Dutreve
its actually not eager loading the second list of accounts If there is no eager loading on the second list, I don't understand why a 'SELECT entries ...' is executed when I just ask account.name and not account.entries. untested, i.e. join_depth on a mapper thats not self-referential,