switch "casade_backrefs" to False by default

Mike Bayer reporter

changed status to wontfix

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 ~~#1973~~ warnings. 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".

2010-11-28T16:49:10+00:00

Comments (3)

Mike Bayer reporter
- changed status to wontfix
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 ~~#1973~~ warnings. 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".
- 2010-11-28T16:49:10+00:00
Mike Bayer reporter
original rev is in e836366c843cd64a0df569582534868e3fb00f3b rollback is in ca9d3cea39a8cd2758ec6981872c38b7b3f59079 (when the bitbucket branch is merged these will highlight)
- 2010-11-28T16:51:04+00:00
Mike Bayer reporter
- removed milestone
Removing milestone: 0.7.0 (automated comment)
- 2014-02-23T18:14:43+00:00
Log in to comment