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
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Nicolas Wavrant
ZODB
Commits
d8ab19de
Commit
d8ab19de
authored
Jun 23, 2007
by
Gary Poster
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
clarification to doc
parent
520c44bd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
3 deletions
+4
-3
src/ZODB/ConflictResolution.txt
src/ZODB/ConflictResolution.txt
+4
-3
No files found.
src/ZODB/ConflictResolution.txt
View file @
d8ab19de
...
...
@@ -9,9 +9,10 @@ Conflict resolution is a way to resolve transaction conflicts that would
otherwise abort a transaction. As such, it risks data integrity in order to
try to avoid throwing away potentially computationally expensive transactions.
The risk of data integrity should not be underestimated. Writing conflict
resolution code takes responsibility away from the ZODB for transactional
integrity, and puts it in the hands of the developer writing the code.
The risk of harming data integrity should not be underestimated. Writing
conflict resolution code takes some responsibility away from the ZODB
for transactional integrity, and puts it in the hands of the developer
writing the conflict resolution code.
The current conflict resolution code is implemented with a storage mix-in
found in ZODB/ConflictResolution.py. The idea's proposal, and an explanation
...
...
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