thanks, this is fixed in 1179. its the same bug over and over
again. inheritance mappers used to make their relationships against
the "inherited table", which is, tableA JOIN tableB JOIN tableC etc.
i.e. all the tables in the inheritance. now it is becoming apparent
that relationships on a mapper must be made only against tableA and
*not* the inherited tables, so this was yet another place where I had
it making a relation against the inheritance join and not the single
mapper's table.
On Mar 21, 2006, at 1:22 PM, Florian Boesch wrote:
I noticed that lazy loading on an n:m relation over an intermediate
table on an
ancestor gives the wrong results. Atached you find the test-program.
<inheritance and lazy.py>
-------------------------------------------------------
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
