]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- The "foreign_keys" argument of relation() will now propagate
authorMike Bayer <mike_mp@zzzcomputing.com>
Sat, 13 Jun 2009 03:31:30 +0000 (03:31 +0000)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sat, 13 Jun 2009 03:31:30 +0000 (03:31 +0000)
commit99d3c5f3356035d7b8fc1c44b411340e5d8c8537
tree3d8af1d5694e7acb8b197f2b03aa9287f4876b7b
parent45cec095b4904ba71425d2fe18c143982dd08f43
- The "foreign_keys" argument of relation() will now propagate
automatically to the backref in the same way that
primaryjoin and secondaryjoin do.   For the extremely
rare use case where the backref of a relation() has
intentionally different "foreign_keys" configured, both sides
now need to be configured explicity (if they do in fact require
this setting, see the next note...).

- ...the only known (and really, really rare) use case where a
different foreign_keys setting was used on the forwards/backwards
side, a composite foreign key that partially points to its own
columns, has been enhanced such that the fk->itself aspect of the
relation won't be used to determine relation direction.
CHANGES
lib/sqlalchemy/orm/properties.py
test/orm/test_relationships.py