its unlikely because i dont consider eager loading from a single table to itself a very viable thing to be doing automatically. if you consider the complexity of query in such a case, it really gets out of hand.
you can of course construct your own query and use query.instances() along with contains_eager() to get exactly the results you want. On Mar 19, 2007, at 12:28 PM, che wrote: > > Thanks Michael, > > Michael Bayer написа: >> On Mar 19, 2007, at 8:29 AM, che wrote: >>> Maybe the problem is that somehow >>> polymorhic and eager cannot be combined? >>> please advice >>> >> >> thats correct, in many cases eager loading will "degrade" to lazy >> loading, particularly when it detects a self-referential table >> relationship (which happens often with polymorphic relationships). >> if you turn on sqlalchemy.orm logging you should see this in the logs >> to confirm. > > unfortunately you are right - in the case of only Address I get in the > logs: > ... > * SA: DEBUG eagerload scalar instance on [EMAIL PROTECTED] > ... > and in the MailAddress case: > ... > * SA: DEBUG degrade to lazy loader on [EMAIL PROTECTED] > * SA: DEBUG set instance-level lazy loader on > [EMAIL PROTECTED] > [* SA: DEBUG Executing lazy callable on [EMAIL PROTECTED] > * SA: DEBUG lazy load attribute address on instance [EMAIL PROTECTED] > ... > Is it possible to workaround this behaviour somehow now (or some plans > for the SA future)? > > regards, > Stefan > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
