From: Evan Taylor Yates Date: Tue, 13 Oct 2020 19:21:30 +0000 (-0700) Subject: Add discussed changes X-Git-Tag: rel_1_4_0b1~28^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F5636%2Fhead;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Add discussed changes PR link: https://github.com/sqlalchemy/sqlalchemy/pull/5636 --- diff --git a/doc/build/orm/cascades.rst b/doc/build/orm/cascades.rst index 8a2a948760..528e69a97b 100644 --- a/doc/build/orm/cascades.rst +++ b/doc/build/orm/cascades.rst @@ -93,12 +93,11 @@ becomes part of the state of that :class:`.Session`:: >>> address3 in sess >>> True -``save-update`` has the possibly surprising behavior which is that -persistent objects which were *removed* from a collection -(or in some cases a scalar attribute) -may also be pulled into the :class:`.Session` of a parent object; this is +A ``save-update`` cascade can exhibit surprising behavior when removing an item from +a collection or de-associating an object from a scalar attribute. In some cases, the +orphaned objects may still be pulled into the ex-parent's :class:`.Session`; this is so that the flush process may handle that related object appropriately. -This case can usually only arise if an object is removed from one :class:`.Session` +This case usually only arises if an object is removed from one :class:`.Session` and added to another:: >>> user1 = sess1.query(User).filter_by(id=1).first()