> 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, im > surprised thats actually doing something. Sign of good design? > basically the way youre trying to get it to eager load *just* the > accounts on the entries on the transaction, and *not* on the entries > off the account itself, is entirely something that has never been > attempted before. So while I will add a trac ticket for this (#777), > more expedient for now would be to construct the exact query you want > and apply it using from_statement() in conjunction with the > contains_eager() option to indicate the eagerly loaded relations. Thanks for your help. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
