On Monday 14 January 2008 18:35:40 Michael Bayer wrote: > On Jan 14, 2008, at 11:29 AM, svilen wrote: > > On Monday 14 January 2008 17:19:14 Michael Bayer wrote: > >> On Jan 14, 2008, at 8:41 AM, svilen wrote: > >>> i have, say, base class A, inherited by two children B and C. B > >>> has an attribute/relation 'address', A and C do not have it. > >>> So i had a query(A).eagerload( 'address') and that did work > >>> before r3912. But later it gives an error - "mapper|A has no > >>> property 'address'". > >>> Any hint how to do it now? > >> > >> what kind of inheritance/mapping from A->B ? i cant really > >> imagine any way that kind of eager load could have worked since > >> the "address" property of "B" does not (and has never) get > >> consulted in that case. > > > > plain joined?... hmm. > > maybe it did not really work (eagerly) but lazy-load has fired > > instead... seems that's the case. > > anyway. > > some way to accomplish such thing? > > no ! this the same issue with the Channel->CatalogChannel thing, yes i guessed it.. > your query is against "A"...attributes that are only on "B" don't > enter into the equation here. this is somewhat different, my query/filter is on attributes that do exist in A; i only want the ORM to postprocess certain things... there will be 'address' column in the result-set anyway (empty or not), why it cannot be eagerloaded via B.address?
> But also, if youre using > select_table, we dont yet support eager loads from a > polymorphic-unioned mapper in any case (though we are close). it is not polymunion, joined_inh works via left-outer-join. well, no is no. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
