[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets
Brought to you by:
zzzeek
From: Bitbucket <com...@bi...> - 2014-07-15 17:22:43
|
2 new commits in sqlalchemy: https://bitbucket.org/zzzeek/sqlalchemy/commits/61384fd0e529/ Changeset: 61384fd0e529 Branch: None User: zzzeek Date: 2014-07-15 19:20:55 Summary: - Fixed a regression caused by :ticket:`2976` released in 0.9.4 where the "outer join" propagation along a chain of joined eager loads would incorrectly convert an "inner join" along a sibling join path into an outer join as well, when only descendant paths should be receiving the "outer join" propagation; additionally, fixed related issue where "nested" join propagation would take place inappropriately between two sibling join paths. this is accomplished by re-introducing the removed flag "allow_innerjoin", now inverted and named "chained_from_outerjoin". Propagating this flag allows us to know when we have encountered an outerjoin along a load path, without confusing it for state obtained from a sibling path. fixes #3131 ref #2976 Affected #: 3 files https://bitbucket.org/zzzeek/sqlalchemy/commits/43663e7aac99/ Changeset: 43663e7aac99 Branch: rel_0_9 User: zzzeek Date: 2014-07-15 19:22:28 Summary: - Fixed a regression caused by :ticket:`2976` released in 0.9.4 where the "outer join" propagation along a chain of joined eager loads would incorrectly convert an "inner join" along a sibling join path into an outer join as well, when only descendant paths should be receiving the "outer join" propagation; additionally, fixed related issue where "nested" join propagation would take place inappropriately between two sibling join paths. this is accomplished by re-introducing the removed flag "allow_innerjoin", now inverted and named "chained_from_outerjoin". Propagating this flag allows us to know when we have encountered an outerjoin along a load path, without confusing it for state obtained from a sibling path. fixes #3131 ref #2976 Affected #: 3 files Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. |