[sqlalchemy] Re: eagerload of inherited polymorphic class via relation

2007-03-24 Thread Rick Morrison
thanks, but either I'm confused, or I wasn't clear. There is no tableB1. The object B1 inherits from B, still using tableB via single-table inheritance. Doing this via lazy load works OK; the where filter is issued. It's not issued if I try to load via eagerload either using .options() or

[sqlalchemy] Re: eagerload of inherited polymorphic class via relation

2007-03-24 Thread Michael Bayer
thats a bug (which I alluded to in my previous email) On Mar 24, 2007, at 4:18 PM, Rick Morrison wrote: thanks, but either I'm confused, or I wasn't clear. There is no tableB1. The object B1 inherits from B, still using tableB via single-table inheritance. Doing this via lazy load works

[sqlalchemy] Re: eagerload of inherited polymorphic class via relation

2007-03-24 Thread sdobrev
On Saturday 24 March 2007 21:35:19 Michael Bayer wrote: On Mar 24, 2007, at 4:38 PM, [EMAIL PROTECTED] wrote: i would also say its slightly better in the case of joined table inheritance to *not* query for the type column as well since it can add weight to the query. hmm, probably. how