nope, options(eagerload('a'), eagerload('a.b')) works just fine, have
tested it here to verify
You're quite correct.. Sorry for the noise. I had tried it a while
back and it didn't work yet. But in between now and then, it has
magically been implemented by you!
Thanks
Dennis
in theory youd say options(eagerload(a.b)).
the separate eagerload(a) isnt needed since its sort of impossible
to eagerload b without eager loading a.
On Mar 9, 2007, at 3:01 PM, Dennis wrote:
I have a class that has a lazy loaded option.
This class is a parent of another table that I'd
On Mar 9, 2:20 pm, Michael Bayer [EMAIL PROTECTED] wrote:
in theory youd say options(eagerload(a.b)).
the separate eagerload(a) isnt needed since its sort of impossible
to eagerload b without eager loading a.
But I'm assuming there isn't a way to do it currently.
I guess I could create a
except im totally wrong, at the moment you have to have the separate
eagerload for each path, the way you have it.
On Mar 9, 2007, at 3:01 PM, Dennis wrote:
I have a class that has a lazy loaded option.
This class is a parent of another table that I'd like to select from.
a-lazy_b
Hi,
I guess I could create a mapper for a that doesn't lazyload b and use
that mapper instead.
I'm doing just that and it works fine for me.
Paul
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
sqlalchemy
