From 696e82702c0deafb4a5f1baf35da8e7987818fd0 Mon Sep 17 00:00:00 2001 From: Renat Akhmerov Date: Wed, 16 May 2018 13:58:10 +0700 Subject: [PATCH] Release note for using "passive_deletes=True" Related-Bug: #1757966 Change-Id: I013d4837603839364f8d699f7ce97e4400879d38 --- ...g_passive_deletes_in_sqlalchemy-4b3006b3aba55155.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/using_passive_deletes_in_sqlalchemy-4b3006b3aba55155.yaml diff --git a/releasenotes/notes/using_passive_deletes_in_sqlalchemy-4b3006b3aba55155.yaml b/releasenotes/notes/using_passive_deletes_in_sqlalchemy-4b3006b3aba55155.yaml new file mode 100644 index 000000000..602ad372b --- /dev/null +++ b/releasenotes/notes/using_passive_deletes_in_sqlalchemy-4b3006b3aba55155.yaml @@ -0,0 +1,9 @@ +--- +fixes: + - | + Used "passive_deletes=True" in the configuration of relationships in + SQLAlchemy models. This improves deletion of graphs of related objects + stored in DB because dependent objects don't get loaded prior to + deleting them. + More about using this flag can be found at: + http://docs.sqlalchemy.org/en/latest/orm/collections.html#using-passive-deletes