for err-disc2.py, that one was something stupid. query was great, the mapper wasnt expecting a blank "eager" row for an inheritance relationship, rev 2257. sort of surprised that one hasnt come up before, its been around a long time.
On Jan 26, 12:16 pm, "Michael Bayer" <[EMAIL PROTECTED]> wrote: > On Jan 26, 9:24 am, svilen <[EMAIL PROTECTED]> wrote: > > > > > It does not happen if inheritance is not involved.right A and B are no > > longer the "same" class if they dont inherit. > > > > > Employee points to Dept and Dept points to Director; Director inherits > > Employee. no other references.thats not the test case im talking about, you > > gave me just "A" and "B" > with "B" point to "A" (which is "A" pointing to "A"). just look at the > queries these things generate, expecting eager in all cases from those > relations is starting to push the envelope a bit further than I can > handle myself (as well as what a DB can usually handle). > > > is there any link between a relation being post_update and being lazy?no. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
