eager loading works with an arbitrary number of levels by joining A-
>B and B->C. it should not be joining A->C, and there are plenty of
tests for this. I would guess that more of your inheritance setups
might be revealing this error, so just send me a test program and
I'll continue to tweak.
On Mar 21, 2006, at 12:03 PM, Florian Boesch wrote:
Simply put, when I got a class A with N Bs, and when I got a class
B with N Cs,
and the relation from A to B is eager as well as the relation from
B to C, I
get all Bs and Cs correlated to this A. However, what I wanted was
just the
baseclass information of the Bs and no correlated information on Cs
whatsoever.
How do you solve this usually in order not to end up throwing away
eager load
benefits and not fetch all correlated things?
Cheers,
Florian
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the
live webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
