- changed status to wontfix
switch "casade_backrefs" to False by default
Issue #1974
resolved
somewhat related to #1973
Comments (3)
-
reporter -
reporter original rev is in e836366c843cd64a0df569582534868e3fb00f3b rollback is in ca9d3cea39a8cd2758ec6981872c38b7b3f59079 (when the bitbucket branch is merged these will highlight)
-
reporter - removed milestone
Removing milestone: 0.7.0 (automated comment)
- Log in to comment
backref between A and B implies an association of A with B, means B associates with A, such as B is present in a collection associated with A. It's expected behavior that if A links to B and A is in the session, B should be in there too. Tried this patch out and got tons of
#1973warnings. This was nice in that a whole bunch of previously silent failures were being warned. But to resolve the warnings is a huge PITA, basically when you previously relied upon cascade, now you have to say "o = object_session(A); if s is not None: s.add(B)". The change is a lot more tedious and dramatic than I expected, so this ticket is a "wontfix".