]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5fedaa0) | patch
Don't null FK for collection-removed item with passive_deletes='all'
authorMike Bayer <mike_mp@zzzcomputing.com>
Wed, 28 Feb 2018 16:50:17 +0000 (11:50 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 11 Jul 2018 18:23:18 +0000 (14:23 -0400)
commit9f09b6ef1807574a1fa9d155d5a80dba455285fd
tree19aad069ed1b092496b8dfe42691f4857b4aa55etree | snapshot
parent5fedaa0eb805eb1032ea1f9e39123bbde3629e52commit | diff
Don't null FK for collection-removed item with passive_deletes='all'

Fixed issue regarding passive_deletes="all", where the foreign key
attribute of an object is maintained with its value even after the object
is removed from its parent collection.  Previously, the unit of work would
set this to NULL even though passive_deletes indicated it should not be
modified.

Change-Id: I5ba98bc388cbdd6323d255b764e02506c2e66896
Fixes: #3844
doc/build/changelog/migration_13.rst diff | blob | blame | history
doc/build/changelog/unreleased_13/3844.rst [new file with mode: 0644] blob
lib/sqlalchemy/orm/dependency.py diff | blob | blame | history
test/orm/test_unitofwork.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git