]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
Remove passive_deletes warning for many-to-one
authorMike Bayer <mike_mp@zzzcomputing.com>
Tue, 2 Mar 2021 23:48:08 +0000 (18:48 -0500)
committerMike Bayer <mike_mp@zzzcomputing.com>
Wed, 3 Mar 2021 15:54:07 +0000 (10:54 -0500)
commit9d4d15e931b76a4c1456c1023e3e61e1663cfe9c
tree67537b44aee71ce6ad91710d37476bd15e03a50d
parent90039d47473afc6de86c4bed521fcd1196b43d18
Remove passive_deletes warning for many-to-one

Removed very old warning that states that passive_deletes is not intended
for many-to-one relationships. While it is likely that in many cases
placing this parameter on a many-to-one relationship is not what was
intended, there are use cases where delete cascade may want to be
disallowed following from such a relationship.

Change-Id: I07adb726633f73f26296add4ec70376d5dcf8817
References: #5983
(cherry picked from commit a63b23392fc31766e32b8650127d9006ee189a0f)
doc/build/changelog/unreleased_13/5983.rst [new file with mode: 0644]
lib/sqlalchemy/orm/relationships.py
test/orm/test_unitofwork.py