diff options
author | Evan Taylor Yates <evantayloryates@gmail.com> | 2020-10-03 17:04:44 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-10-03 17:04:44 -0700 |
commit | c6eca2271770308bac2747f0c32030ffaf8d7747 (patch) | |
tree | b599ea94dc658e75cc60b16962eba0a7543821b8 | |
parent | 7bb9ea911cb2e573696a91392a6a08161950ac9f (diff) | |
download | sqlalchemy-c6eca2271770308bac2747f0c32030ffaf8d7747.tar.gz |
Add parens around unmarked clause
I'm not 100% sure what this sentence is saying, but I'm pretty sure it needs either commas or parentheses to break it up a little. I think parens make the most sense in this case assuming I am reading it correctly. Here's the original sentence and proposed edit in plaintext:
ORIG
"...persistent objects which were removed from a collection or in some cases a scalar attribute may also be pulled into the Session of a parent object;..."
EDIT
"...persistent objects which were removed from a collection (or in some cases a scalar attribute) may also be pulled into the Session of a parent object;..."
-rw-r--r-- | doc/build/orm/cascades.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/build/orm/cascades.rst b/doc/build/orm/cascades.rst index 3f06b34c2..8a2a94876 100644 --- a/doc/build/orm/cascades.rst +++ b/doc/build/orm/cascades.rst @@ -95,7 +95,7 @@ becomes part of the state of that :class:`.Session`:: ``save-update`` has the possibly surprising behavior which is that persistent objects which were *removed* from a collection -or in some cases a scalar attribute +(or in some cases a scalar attribute) may also be pulled into the :class:`.Session` of a parent object; this is so that the flush process may handle that related object appropriately. This case can usually only arise if an object is removed from one :class:`.Session` |