]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
projects / thirdparty / sqlalchemy / sqlalchemy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: fd4c414) | patch
- assert passive_deletes='all' does not affect collection/scalar
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 6 Jun 2017 22:53:03 +0000 (18:53 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 7 Jun 2017 13:46:10 +0000 (09:46 -0400)
commit3ded82817e52e6cf070d1bd25a7094d886d0fd33
tree668558e8cb118ddaa0ee69d2f405808040eb138btree | snapshot
parentfd4c414572f503e5393daeef6d5c9e7dac7d3f26commit | diff
- assert passive_deletes='all' does not affect collection/scalar
membership removal

in issue #3844 we hypotheized that passive_deletes='all' was broken
because it sets to NULL a foreign key attribute when the child
object is removed or replaced.   However, not doing the NULL
set means that nothing happens at all and the operation silently
fails.

Change-Id: I11834e7e324349e172dc797bac62731008b6b95a
(cherry picked from commit acf64c4178169b765f3f7ae492b1774955cf541f)
lib/sqlalchemy/orm/relationships.py diff | blob | blame | history
test/orm/test_unitofwork.py diff | blob | blame | history
Mirror of https://github.com/sqlalchemy/sqlalchemy.git