Commit 120f182d authored by Leonard Norrgrd's avatar Leonard Norrgrd

Wording, typo.

parent 458e167e
...@@ -79,8 +79,8 @@ happens. Consider: ...@@ -79,8 +79,8 @@ happens. Consider:
>>> p2.p4 = p4 >>> p2.p4 = p4
In this example, the new object is reachable from both `p1` in database In this example, the new object is reachable from both `p1` in database
1 and `p2` in database 2. If we commit, which database will `p4` end up 1 and `p2` in database 2. If we commit, which database should `p4` end up
in? This sort of ambiguity can lead to subtle bugs. For that reason, in? This sort of ambiguity could lead to subtle bugs. For that reason,
an error is generated if we commit changes when new objects are an error is generated if we commit changes when new objects are
reachable from multiple databases: reachable from multiple databases:
...@@ -120,8 +120,7 @@ This doesn't work with a savepoint: ...@@ -120,8 +120,7 @@ This doesn't work with a savepoint:
(Maybe it should.) (Maybe it should.)
We can disambiguate this situation by using the connection add method We can disambiguate this situation by using the connection add method
to explicitly say waht database an object belongs to: to explicitly say what database an object belongs to:
>>> p5 = MyClass() >>> p5 = MyClass()
>>> p1.p5 = p5 >>> p1.p5 = p5
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment