PublicArchive/sqlalchemy
2
0
Fork 0
mirror of https://github.com/sqlalchemy/sqlalchemy.git synced 2026-05-16 05:37:16 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/pr/5636'

Browse Source 
Change-Id: I785a3c8a49f2d75279ade65bd86915de1178a3ff
This commit is contained in:
Mike Bayer
2020-10-14 16:37:40 -04:00
parent 2555f095d0 7740ce6900
commit f2615fac0b
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/build/orm/cascades.rst
Vendored
+4 -5
View File
@@ -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()