From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 9 Jan 2023 17:38:10 +0000 (-0500)
Subject: remove misleading line in post_update
X-Git-Tag: rel_1_4_47~24
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=13a5e3ac1ca93e09535f026fc8b9ce36dfbeeb14;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

remove misleading line in post_update

this UPDATE refers to the unit of work's need to consider this
additional UPDATE as a dependency and not an actual UPDATE statement.

Change-Id: I2a520af21ebf96b45c431efa898d4e7683a5bc2d
References: #9066
References: #1063
(cherry picked from commit 2ef4b449a7709ecab45e926f0e8d0dd398fd12db)
---

diff --git a/lib/sqlalchemy/orm/relationships.py b/lib/sqlalchemy/orm/relationships.py
index c85323a2b4..d19420ab85 100644
--- a/lib/sqlalchemy/orm/relationships.py
+++ b/lib/sqlalchemy/orm/relationships.py
@@ -758,9 +758,7 @@ class RelationshipProperty(StrategizedProperty):
         :param post_update:
           This indicates that the relationship should be handled by a
           second UPDATE statement after an INSERT or before a
-          DELETE. Currently, it also will issue an UPDATE after the
-          instance was UPDATEd as well, although this technically should
-          be improved. This flag is used to handle saving bi-directional
+          DELETE. This flag is used to handle saving bi-directional
           dependencies between two individual rows (i.e. each row
           references the other), where it would otherwise be impossible to
           INSERT or DELETE both rows fully since one row exists before the