Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
zodb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Joshua
zodb
Commits
120f182d
Commit
120f182d
authored
Feb 22, 2008
by
Leonard Norrgrd
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Wording, typo.
parent
458e167e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
4 deletions
+3
-4
src/ZODB/cross-database-references.txt
src/ZODB/cross-database-references.txt
+3
-4
No files found.
src/ZODB/cross-database-references.txt
View file @
120f182d
...
...
@@ -79,8 +79,8 @@ happens. Consider:
>>> p2.p4 = p4
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
in? This sort of ambiguity c
an lead to subtle bugs.
For that reason,
1 and `p2` in database 2. If we commit, which database
should
`p4` end up
in? This sort of ambiguity c
ould lead to subtle bugs.
For that reason,
an error is generated if we commit changes when new objects are
reachable from multiple databases:
...
...
@@ -120,8 +120,7 @@ This doesn't work with a savepoint:
(Maybe it should.)
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()
>>> p1.p5 = p5
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment