]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
relationships no longer compile against the "selectable" mapper (i.e. the polymorphic...
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 23 Jan 2007 04:05:07 +0000 (04:05 +0000)
committerMike Bayer <mike_mp@zzzcomputing.com>
Tue, 23 Jan 2007 04:05:07 +0000 (04:05 +0000)
commit30f75c2157478480c54ca65d2a00ec1ed6a8820e
treec94aa42baccc2d5bef90bd2e3084aa2a930f4b90
parentcaabadf86666256d1626b84e512fd66bad52fb50
relationships no longer compile against the "selectable" mapper (i.e. the polymorphic mapper).  join conditions, foreign keys etc. are configured against the actual mappers used in the relationship in all cases.  the lazy and eager loaders in turn "adapt" their lazy/eager clauses to that of the "selectable" mapper if one is present.  this is because the join conditions between the mapper's base tables are *far* easier to work with and detect direction etc. compared to an enormous polymorphic union; dealing with the polymorphic union is pushed further out into select query construction.
CHANGES
lib/sqlalchemy/orm/properties.py
lib/sqlalchemy/orm/strategies.py
lib/sqlalchemy/sql_util.py
test/orm/inheritance5.py
test/orm/poly_linked_list.py
test/orm/polymorph.py