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
Kirill Smelkov
ZODB
Commits
9a7ddcbe
Commit
9a7ddcbe
authored
Sep 13, 2016
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos in 'synchronizers' tests
parent
c75a197d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
src/ZODB/tests/synchronizers.txt
src/ZODB/tests/synchronizers.txt
+4
-4
No files found.
src/ZODB/tests/synchronizers.txt
View file @
9a7ddcbe
...
@@ -26,7 +26,7 @@ Make a change locally:
...
@@ -26,7 +26,7 @@ Make a change locally:
>>> rt = cn.root()
>>> rt = cn.root()
>>> rt['a'] = 1
>>> rt['a'] = 1
Sync isn't called when a connecti
i
n is opened, even though that
Sync isn't called when a connecti
o
n is opened, even though that
implicitly starts a new transaction:
implicitly starts a new transaction:
>>> st.sync_called
>>> st.sync_called
...
@@ -40,7 +40,7 @@ Sync is only called when we explicitly start a new transaction:
...
@@ -40,7 +40,7 @@ Sync is only called when we explicitly start a new transaction:
True
True
>>> st.sync_called = False
>>> st.sync_called = False
BTW, calling ``sync()`` on a connectin starts a new transaction, which
BTW, calling ``sync()`` on a connecti
o
n starts a new transaction, which
caused ``sync()`` to be called on the storage:
caused ``sync()`` to be called on the storage:
>>> cn.sync()
>>> cn.sync()
...
@@ -49,7 +49,7 @@ caused ``sync()`` to be called on the storage:
...
@@ -49,7 +49,7 @@ caused ``sync()`` to be called on the storage:
>>> st.sync_called = False
>>> st.sync_called = False
``sync()`` is not called by the Connection's ``afterCompletion()``
``sync()`` is not called by the Connection's ``afterCompletion()``
hook after the commit completes, because we'll s
u
nc when a new
hook after the commit completes, because we'll s
y
nc when a new
transaction begins:
transaction begins:
>>> transaction.commit()
>>> transaction.commit()
...
@@ -81,7 +81,7 @@ traceback then ;-)
...
@@ -81,7 +81,7 @@ traceback then ;-)
>>> cn.close()
>>> cn.close()
As a special case, if a synchronizer registers while a transaction is
As a special case, if a synchronizer registers while a transaction is
in flight, then newTransaction and th
i
s the storage sync method is
in flight, then newTransaction and th
u
s the storage sync method is
called:
called:
>>> tm = transaction.TransactionManager()
>>> tm = transaction.TransactionManager()
...
...
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