Skip to content

Z
ZEO
Commit 306edcf3 authored by Tim Peters's avatar Tim Peters
Browse files
Options

Removed Transaction.py. The new transaction package takes its place. 

get_transaction() is still stuffed into __builtin__ as a magical side
effect of importing ZODB.
parent f9900afe
Hide whitespace changes
Inline Side-by-side
Showing with 56 additions and 611 deletions
src/ZODB/Transaction.py deleted 100644 → 0
View file @ f9900afe
##############################################################################
#
# Copyright (c) 2001, 2002 Zope Corporation and Contributors.
# All Rights Reserved.
#
# This software is subject to the provisions of the Zope Public License,
# Version 2.0 (ZPL). A copy of the ZPL should accompany this distribution.
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED
# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS
# FOR A PARTICULAR PURPOSE
#
##############################################################################
"""Transaction management
$Id: Transaction.py,v 1.59 2004/04/01 03:56:58 jeremy Exp $
"""
import sys
from thread import get_ident as _get_ident
from zLOG import LOG, ERROR, PANIC, INFO, BLATHER, WARNING
from ZODB.POSException import TransactionError
from ZODB.utils import oid_repr
# Flag indicating whether certain errors have occurred.
hosed = 0
# There is an order imposed on all jars, based on the storages they
# serve, that must be consistent across all applications using the
# storages. The order is defined by the sortKey() method of the jar.
def jar_cmp(j1, j2):
# Call sortKey() every time, because a ZEO client could reconnect
# to a different server at any time.
try:
k1 = j1.sortKey()
except:
LOG("TM", WARNING, "jar missing sortKey() method: %s" % j1)
k1 = id(j1)
try:
k2 = j2.sortKey()
except:
LOG("TM", WARNING, "jar missing sortKey() method: %s" % j2)
k2 = id(j2)
return cmp(k1, k2)
class Transaction:
user = ''
description = ''
_connections = None
_extension = None
_sub = None # This is a subtrasaction flag
# The _non_st_objects variable is either None or a list
# of jars that do not support subtransactions. This is used to
# manage non-subtransaction-supporting jars during subtransaction
# commits and aborts to ensure that they are correctly committed
# or aborted in the "outside" transaction.
_non_st_objects=None
def __init__(self, id=None):
self._id=id
self._objects=[]
self._append=self._objects.append
raise RuntimeError
def _init(self):
self._objects=[]
self._append=self._objects.append
self.user=self.description=''
if self._connections:
for c in self._connections.values(): c.close()
del self._connections
def log(self, msg, level=INFO, error=None):
LOG("TM:%s" % self._id, level, msg, error=error)
def sub(self):
# Create a manually managed subtransaction for internal use
r=self.__class__()
r.user=self.user
r.description=self.description
r._extension=self._extension
return r
def __str__(self):
if self._id is None:
return "Transaction user=%s" % `self.user`
else:
return "Transaction thread=%s user=%s" % (self._id, `self.user`)
# XXX This whole freeme business is lame.
# As a separate task, we really need to revisit transaction management.
def __del__(self):
if self._objects:
self.abort(freeme=0)
def abort(self, subtransaction=0, freeme=1):
"""Abort the transaction.
This is called from the application. This means that we haven't
entered two-phase commit yet, so no tpc_ messages are sent.
"""
if subtransaction and (self._non_st_objects is not None):
raise TransactionError(
"""Attempted to abort a sub-transaction, but a participating
data manager doesn't support partial abort.
""")
t = None
if not subtransaction:
# Must add in any non-subtransaction supporting objects that
# may have been stowed away from previous subtransaction
# commits.
if self._non_st_objects is not None:
self._objects.extend(self._non_st_objects)
self._non_st_objects = None
if self._sub is not None:
# Abort of top-level transaction after commiting
# subtransactions.
subjars = self._sub.values()
subjars.sort(jar_cmp)
self._sub = None
else:
subjars = []
try:
# Abort the objects
for o in self._objects:
try:
j = getattr(o, '_p_jar', o)
if j is not None:
j.abort(o, self)
except:
# Record the first exception that occurred
if t is None:
t, v, tb = sys.exc_info()
else:
self.log("Failed to abort object %s" %
oid_repr(o._p_oid), error=sys.exc_info())
# tpc_begin() was never called, so tpc_abort() should not be
# called.
if not subtransaction:
# abort_sub() must be called to clear subtransaction state
for jar in subjars:
jar.abort_sub(self) # This should never fail
if t is not None:
raise t, v, tb
finally:
if t is not None:
del tb # don't keep traceback in local variable
del self._objects[:] # Clear registered
if not subtransaction and freeme:
if self._id is not None:
free_transaction()
else:
self._init()
def begin(self, info=None, subtransaction=None):
"""Begin a new transaction.
This aborts any transaction in progres.
"""
if self._objects:
self.abort(subtransaction, 0)
if info:
L = info.split("\t")
self.user = L[0].strip()
self.description = "\t".join(L[1:]).strip()
def commit(self, subtransaction=None):
"""Finalize the transaction."""
objects = self._objects
subjars = []
if subtransaction:
if self._sub is None:
# Must store state across multiple subtransactions
# so that the final commit can commit all subjars.
self._sub = {}
else:
if self._sub is not None:
# This commit is for a top-level transaction that
# has previously committed subtransactions. Do
# one last subtransaction commit to clear out the
# current objects, then commit all the subjars.
if objects:
self.commit(1)
objects = []
subjars = self._sub.values()
subjars.sort(jar_cmp)
self._sub = None
# If there were any non-subtransaction-aware jars
# involved in earlier subtransaction commits, we need
# to add them to the list of jars to commit.
if self._non_st_objects is not None:
objects.extend(self._non_st_objects)
self._non_st_objects = None
if (objects or subjars) and hosed:
# Something really bad happened and we don't
# trust the system state.
raise TransactionError(hosed_msg)
# It's important that:
#
# - Every object in self._objects is either committed or
# aborted.
#
# - For each object that is committed we call tpc_begin on
# it's jar at least once
#
# - For every jar for which we've called tpc_begin on, we
# either call tpc_abort or tpc_finish. It is OK to call
# these multiple times, as the storage is required to ignore
# these calls if tpc_begin has not been called.
#
# - That we call tpc_begin() in a globally consistent order,
# so that concurrent transactions involving multiple storages
# do not deadlock.
try:
ncommitted = 0
jars = self._get_jars(objects, subtransaction)
try:
# If not subtransaction, then jars will be modified.
self._commit_begin(jars, subjars, subtransaction)
ncommitted += self._commit_objects(objects)
if not subtransaction:
# Unless this is a really old jar that doesn't
# implement tpc_vote(), it must raise an exception
# if it can't commit the transaction.
for jar in jars:
try:
vote = jar.tpc_vote
except AttributeError:
pass
else:
vote(self)
# Handle multiple jars separately. If there are
# multiple jars and one fails during the finish, we
# mark this transaction manager as hosed.
if len(jars) == 1:
self._finish_one(jars[0])
else:
self._finish_many(jars)
except:
self._cleanup(objects, ncommitted, jars, subjars)
finally:
del objects[:] # clear registered
if not subtransaction and self._id is not None:
free_transaction()
def _cleanup(self, objects, ncommitted, jars, subjars):
# Ugh, we got an got an error during commit, so we
# have to clean up. First save the original exception
# in case the cleanup process causes another
# exception.
error = sys.exc_info()
try:
self._commit_error(objects, ncommitted, jars, subjars)
except:
LOG("ZODB", ERROR,
"A storage error occured during transaction "
"abort. This shouldn't happen.",
error=sys.exc_info())
raise error[0], error[1], error[2]
def _get_jars(self, objects, subtransaction):
# Returns a list of jars for this transaction.
# Find all the jars and sort them in a globally consistent order.
# objects is a list of persistent objects and jars.
# If this is a subtransaction and a jar is not subtransaction aware,
# it's object gets delayed until the parent transaction commits.
d = {}
for o in objects:
jar = getattr(o, '_p_jar', o)
if jar is None:
# I don't think this should ever happen, but can't
# prove that it won't. If there is no jar, there
# is nothing to be done.
self.log("Object with no jar registered for transaction: "
"%s" % repr(o), level=BLATHER)
continue
# jar may not be safe as a dictionary key
key = id(jar)
d[key] = jar
if subtransaction:
if hasattr(jar, "commit_sub"):
self._sub[key] = jar
else:
if self._non_st_objects is None:
self._non_st_objects = []
self._non_st_objects.append(o)
jars = d.values()
jars.sort(jar_cmp)
return jars
def _commit_begin(self, jars, subjars, subtransaction):
if subtransaction:
assert not subjars
for jar in jars:
try:
jar.tpc_begin(self, subtransaction)
except TypeError:
# Assume that TypeError means that tpc_begin() only
# takes one argument, and that the jar doesn't
# support subtransactions.
jar.tpc_begin(self)
else:
# Merge in all the jars used by one of the subtransactions.
# When the top-level subtransaction commits, the tm must
# call commit_sub() for each jar involved in one of the
# subtransactions. The commit_sub() method should call
# tpc_begin() on the storage object.
# It must also call tpc_begin() on jars that were used in
# a subtransaction but don't support subtransactions.
# These operations must be performed on the jars in order.
# Modify jars inplace to include the subjars, too.
jars += subjars
jars.sort(jar_cmp)
# assume that subjars is small, so that it's cheaper to test
# whether jar in subjars than to make a dict and do has_key.
for jar in jars:
if jar in subjars:
jar.commit_sub(self)
else:
jar.tpc_begin(self)
def _commit_objects(self, objects):
ncommitted = 0
for o in objects:
jar = getattr(o, "_p_jar", o)
if jar is None:
continue
jar.commit(o, self)
ncommitted += 1
return ncommitted
def _finish_one(self, jar):
try:
# The database can't guarantee consistency if call fails.
jar.tpc_finish(self)
except:
# Bug if it does, we need to keep track of it
LOG('ZODB', PANIC,
"A storage error occurred in the last phase of a "
"two-phase commit. This shouldn\'t happen. ",
error=sys.exc_info())
raise
def _finish_many(self, jars):
global hosed
try:
for jar in jars:
# The database can't guarantee consistency if call fails.
jar.tpc_finish(self)
except:
# XXX We should consult ZConfig to decide whether we want to put
# the transaction manager in a hosed state or not.
#hosed = 1
LOG('ZODB', PANIC,
"A storage error occurred in the last phase of a "
"two-phase commit. This shouldn\'t happen. "
"The application will not be allowed to commit "
"until the site/storage is reset by a restart. ",
error=sys.exc_info())
raise
def _commit_error(self, objects, ncommitted, jars, subjars):
# First, we have to abort any uncommitted objects. The abort
# will mark the object for invalidation, so that it's last
# committed state will be restored.
for o in objects[ncommitted:]:
try:
j = getattr(o, '_p_jar', o)
if j is not None:
j.abort(o, self)
except:
# nothing to do but log the error
self.log("Failed to abort object %s" % oid_repr(o._p_oid),
error=sys.exc_info())
# Abort the two-phase commit. It's only necessary to abort the
# commit for jars that began it, but it is harmless to abort it
# for all.
for j in jars:
try:
j.tpc_abort(self) # This should never fail
except:
LOG('ZODB', ERROR,
"A storage error occured during object abort. This "
"shouldn't happen. ", error=sys.exc_info())
# After the tpc_abort(), call abort_sub() on all the
# subtrans-aware jars to *really* abort the subtransaction.
# Example: For Connection(), the tpc_abort() will abort the
# subtransaction TmpStore() and abort_sub() will remove the
# TmpStore.
for j in subjars:
try:
j.abort_sub(self) # This should never fail
except:
LOG('ZODB', ERROR,
"A storage error occured during sub-transaction "
"object abort. This shouldn't happen.",
error=sys.exc_info())
def register(self,object):
'Register the given object for transaction control.'
self._append(object)
def join(self, zodb4datamanager):
"""Join a transaction.interfaces.IDataManager with the transaction
This method is provided for "backward-compatability" with ZODB 4
data managers.
"""
self._append(DataManagerAdapter(zodb4datamanager))
def note(self, text):
if self.description:
self.description = "%s\n\n%s" % (self.description, text.strip())
else:
self.description = text.strip()
def setUser(self, user_name, path='/'):
self.user = "%s %s" % (path, user_name)
def setExtendedInfo(self, name, value):
if self._extension is None:
self._extension = {}
self._extension[name] = value
hosed_msg = \
"""A serious error, which was probably a system error,
occurred in a previous database transaction. This
application may be in an invalid state and must be
restarted before database updates can be allowed.
Beware though that if the error was due to a serious
system problem, such as a disk full condition, then
the application may not come up until you deal with
the system problem. See your application log for
information on the error that lead to this problem.
"""
class DataManagerAdapter(object):
"""Adapt zodb 4-style data managers to zodb3 style
Adapt transaction.interfaces.IDataManager to
ZODB.interfaces.IPureDatamanager
"""
# Note that it is pretty important that this does not have a _p_jar
# attribute. This object will be registered with a zodb3 TM, which
# will then try to get a _p_jar from it, using it as the default.
# (Objects without a _p_jar are their own data managers.)
def __init__(self, datamanager):
self._datamanager = datamanager
self._rollback = None
def commit(self, ob, transaction):
assert ob is self
def abort(self, ob, transaction):
assert ob is self
# We need to discard any changes since the last save point, or all
# changes
if self._rollback is None:
# No previous savepoint, so just abort
self._datamanager.abort(transaction)
else:
self._rollback()
def abort_sub(self, transaction):
self._datamanager.abort(transaction)
def commit_sub(self, transaction):
# Nothing to do wrt data, be we begin 2pc for the top-level
# trans
self._sub = False
def tpc_begin(self, transaction, subtransaction=False):
self._sub = subtransaction
def tpc_abort(self, transaction):
if self._sub:
self.abort(self, transaction)
else:
self._datamanager.abort(transaction)
def tpc_finish(self, transaction):
if self._sub:
self._rollback = self._datamanager.savepoint(transaction).rollback
else:
self._datamanager.commit(transaction)
def tpc_vote(self, transaction):
if not self._sub:
self._datamanager.prepare(transaction)
############################################################################
# install get_transaction:
### Map thread ident to its Transaction instance.
##_tid2tran = {}
### Get Transaction associated with current thread; if none, create a
### new Transaction and return it.
##def get_transaction():
## tid = _get_ident()
## result = _tid2tran.get(tid)
## if result is None:
## _tid2tran[tid] = result = Transaction(tid)
## return result
### Forget whatever Transaction (if any) is associated with current thread.
##def free_transaction():
## tid = _get_ident()
## try:
## del _tid2tran[tid]
## except KeyError:
## pass
from transaction import get as get_transaction
import __builtin__
__builtin__.get_transaction = get_transaction
del __builtin__
src/ZODB/__init__.py
View file @ 306edcf3
...@@ -15,11 +15,16 @@ ...@@ -15,11 +15,16 @@
__version__ = "3.3a2" __version__ = "3.3a2"
import sys import sys
import __builtin__
from persistent import TimeStamp from persistent import TimeStamp
from DB import DB from DB import DB
import Transaction from transaction import get as get_transaction
# Backward compat for old imports. I don't think TimeStamp should # Backward compat for old imports. I don't think TimeStamp should
# really be in persistent anyway # really be in persistent anyway.
sys.modules['ZODB.TimeStamp'] = sys.modules['persistent.TimeStamp'] sys.modules['ZODB.TimeStamp'] = sys.modules['persistent.TimeStamp']
# XXX Issue deprecation warning if this variant is used?
__builtin__.get_transaction = get_transaction
del __builtin__
src/ZODB/tests/testPersistentMapping.py
View file @ 306edcf3
...@@ -24,7 +24,7 @@ import unittest ...@@ -24,7 +24,7 @@ import unittest
import ZODB import ZODB
from ZODB.MappingStorage import MappingStorage from ZODB.MappingStorage import MappingStorage
from ZODB.Transaction import Transaction from transaction import Transaction
import cPickle import cPickle
import cStringIO import cStringIO
import sys import sys
......
src/ZODB/tests/test_datamanageradapter.py
View file @ 306edcf3
...@@ -13,11 +13,11 @@ ...@@ -13,11 +13,11 @@
############################################################################## ##############################################################################
"""XXX short summary goes here. """XXX short summary goes here.
$Id: test_datamanageradapter.py,v 1.3 2004/03/11 15:57:57 jeremy Exp $ $Id: test_datamanageradapter.py,v 1.4 2004/04/05 18:48:22 tim_one Exp $
""" """
import unittest import unittest
from doctest import DocTestSuite from doctest import DocTestSuite
from ZODB.Transaction import DataManagerAdapter from transaction._transaction import DataManagerAdapter
from ZODB.tests.sampledm import DataManager from ZODB.tests.sampledm import DataManager
def test_normal_commit(): def test_normal_commit():
...@@ -34,7 +34,7 @@ def test_normal_commit(): ...@@ -34,7 +34,7 @@ def test_normal_commit():
Now we'll commit the changes. When the data manager joins a transaction, Now we'll commit the changes. When the data manager joins a transaction,
the transaction will create an adapter. the transaction will create an adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -54,7 +54,7 @@ def test_normal_commit(): ...@@ -54,7 +54,7 @@ def test_normal_commit():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -77,7 +77,7 @@ def test_normal_commit(): ...@@ -77,7 +77,7 @@ def test_normal_commit():
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
and the data manager finishes the two-phase commit: and the data manager finishes the two-phase commit:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(1, 0) (1, 0)
>>> dm.prepared >>> dm.prepared
...@@ -98,7 +98,7 @@ def test_abort(): ...@@ -98,7 +98,7 @@ def test_abort():
When the data manager joins a transaction, When the data manager joins a transaction,
the transaction will create an adapter. the transaction will create an adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. and register it as a modified object.
...@@ -116,7 +116,7 @@ def test_abort(): ...@@ -116,7 +116,7 @@ def test_abort():
Then the transaction will call abort on the jar: Then the transaction will call abort on the jar:
>>> t1 = '1' >>> t1 = '1'
>>> jar.abort(dma, t1) >>> jar.abort(t1)
Which aborts the changes in the data manager: Which aborts the changes in the data manager:
...@@ -138,7 +138,7 @@ def test_tpc_abort_phase1(): ...@@ -138,7 +138,7 @@ def test_tpc_abort_phase1():
Now we'll commit the changes. When the data manager joins a transaction, Now we'll commit the changes. When the data manager joins a transaction,
the transaction will create an adapter. the transaction will create an adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -158,7 +158,7 @@ def test_tpc_abort_phase1(): ...@@ -158,7 +158,7 @@ def test_tpc_abort_phase1():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -189,7 +189,7 @@ def test_tpc_abort_phase2(): ...@@ -189,7 +189,7 @@ def test_tpc_abort_phase2():
Now we'll commit the changes. When the data manager joins a transaction, Now we'll commit the changes. When the data manager joins a transaction,
the transaction will create an adapter. the transaction will create an adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -209,7 +209,7 @@ def test_tpc_abort_phase2(): ...@@ -209,7 +209,7 @@ def test_tpc_abort_phase2():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -254,7 +254,7 @@ def test_commit_w_subtransactions(): ...@@ -254,7 +254,7 @@ def test_commit_w_subtransactions():
Now we'll commit the changes in a subtransaction. When the data Now we'll commit the changes in a subtransaction. When the data
manager joins a transaction, the transaction will create an manager joins a transaction, the transaction will create an
adapter. adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -274,7 +274,7 @@ def test_commit_w_subtransactions(): ...@@ -274,7 +274,7 @@ def test_commit_w_subtransactions():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -304,7 +304,7 @@ def test_commit_w_subtransactions(): ...@@ -304,7 +304,7 @@ def test_commit_w_subtransactions():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -313,7 +313,7 @@ def test_commit_w_subtransactions(): ...@@ -313,7 +313,7 @@ def test_commit_w_subtransactions():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -328,13 +328,13 @@ def test_commit_w_subtransactions(): ...@@ -328,13 +328,13 @@ def test_commit_w_subtransactions():
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 5) (0, 5)
and then commit the top-level transaction. and then commit the top-level transaction.
The transaction will actually go through the steps for a subtransaction: The transaction will actually go through the steps for a subtransaction:
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
...@@ -350,7 +350,7 @@ def test_commit_w_subtransactions(): ...@@ -350,7 +350,7 @@ def test_commit_w_subtransactions():
The transaction manager doesn's call tpc_begin, because commit_sub The transaction manager doesn's call tpc_begin, because commit_sub
implies the start of two-phase commit. Next, it does call commit: implies the start of two-phase commit. Next, it does call commit:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
which doesn't do anything. which doesn't do anything.
...@@ -370,7 +370,7 @@ def test_commit_w_subtransactions(): ...@@ -370,7 +370,7 @@ def test_commit_w_subtransactions():
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
and the data manager finishes the two-phase commit: and the data manager finishes the two-phase commit:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(5, 0) (5, 0)
>>> dm.prepared >>> dm.prepared
...@@ -392,7 +392,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -392,7 +392,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
Now we'll commit the changes in a subtransaction. When the data Now we'll commit the changes in a subtransaction. When the data
manager joins a transaction, the transaction will create an manager joins a transaction, the transaction will create an
adapter. adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -412,7 +412,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -412,7 +412,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -442,13 +442,13 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -442,13 +442,13 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
...@@ -457,19 +457,19 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -457,19 +457,19 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
The transaction will just call abort as usual: The transaction will just call abort as usual:
>>> jar.abort(dma, t1) >>> jar.abort(t1)
This will cause a rollback to the last savepoint: This will cause a rollback to the last savepoint:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
Then we do more work: Then we do more work:
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -484,13 +484,13 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -484,13 +484,13 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 5) (0, 5)
and then commit the top-level transaction. and then commit the top-level transaction.
The transaction will actually go through the steps for a subtransaction: The transaction will actually go through the steps for a subtransaction:
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
...@@ -506,7 +506,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -506,7 +506,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
The transaction manager doesn's call tpc_begin, because commit_sub The transaction manager doesn's call tpc_begin, because commit_sub
implies the start of two-phase commit. Next, it does call commit: implies the start of two-phase commit. Next, it does call commit:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
which doesn't do anything. which doesn't do anything.
...@@ -526,7 +526,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort(): ...@@ -526,7 +526,7 @@ def test_commit_w_subtransactions_featuring_subtransaction_abort():
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
and the data manager finishes the two-phase commit: and the data manager finishes the two-phase commit:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(5, 0) (5, 0)
>>> dm.prepared >>> dm.prepared
...@@ -548,7 +548,7 @@ def test_abort_w_subtransactions(): ...@@ -548,7 +548,7 @@ def test_abort_w_subtransactions():
Now we'll commit the changes in a subtransaction. When the data Now we'll commit the changes in a subtransaction. When the data
manager joins a transaction, the transaction will create an manager joins a transaction, the transaction will create an
adapter. adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -568,7 +568,7 @@ def test_abort_w_subtransactions(): ...@@ -568,7 +568,7 @@ def test_abort_w_subtransactions():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -598,7 +598,7 @@ def test_abort_w_subtransactions(): ...@@ -598,7 +598,7 @@ def test_abort_w_subtransactions():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -607,7 +607,7 @@ def test_abort_w_subtransactions(): ...@@ -607,7 +607,7 @@ def test_abort_w_subtransactions():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -622,18 +622,18 @@ def test_abort_w_subtransactions(): ...@@ -622,18 +622,18 @@ def test_abort_w_subtransactions():
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 5) (0, 5)
and then abort the top-level transaction. and then abort the top-level transaction.
The transaction first call abort on the jar: The transaction first call abort on the jar:
>>> jar.abort(dma, t1) >>> jar.abort(t1)
This will have the effect of aborting the subtrancation: This will have the effect of aborting the subtrancation:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
Then the transaction will call abort_sub: Then the transaction will call abort_sub:
>>> jar.abort_sub(t1) >>> jar.abort_sub(t1)
...@@ -660,7 +660,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -660,7 +660,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
Now we'll commit the changes in a subtransaction. When the data Now we'll commit the changes in a subtransaction. When the data
manager joins a transaction, the transaction will create an manager joins a transaction, the transaction will create an
adapter. adapter.
>>> dma = DataManagerAdapter(dm) >>> dma = DataManagerAdapter(dm)
and register it as a modified object. At commit time, the and register it as a modified object. At commit time, the
...@@ -680,7 +680,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -680,7 +680,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
Then the transaction will call commit on the jar: Then the transaction will call commit on the jar:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
This doesn't actually do anything. :) This doesn't actually do anything. :)
...@@ -710,13 +710,13 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -710,13 +710,13 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
...@@ -725,19 +725,19 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -725,19 +725,19 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
The transaction will just call abort as usual: The transaction will just call abort as usual:
>>> jar.abort(dma, t1) >>> jar.abort(t1)
This will cause a rollback to the last savepoint: This will cause a rollback to the last savepoint:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 2) (0, 2)
Then we do more work: Then we do more work:
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 3) (0, 3)
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
>>> dm.state, dm.delta >>> dm.state, dm.delta
...@@ -752,13 +752,13 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -752,13 +752,13 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
>>> dm.inc() >>> dm.inc()
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 5) (0, 5)
and then commit the top-level transaction. and then commit the top-level transaction.
The transaction will actually go through the steps for a subtransaction: The transaction will actually go through the steps for a subtransaction:
>>> jar.tpc_begin(t1, 1) # 1 -> subtxn >>> jar.tpc_begin(t1, 1) # 1 -> subtxn
>>> jar.commit(dma, t1) >>> jar.commit(t1)
>>> jar.tpc_vote(t1) >>> jar.tpc_vote(t1)
>>> jar.tpc_finish(t1) >>> jar.tpc_finish(t1)
...@@ -774,7 +774,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -774,7 +774,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
The transaction manager doesn's call tpc_begin, because commit_sub The transaction manager doesn's call tpc_begin, because commit_sub
implies the start of two-phase commit. Next, it does call commit: implies the start of two-phase commit. Next, it does call commit:
>>> jar.commit(dma, t1) >>> jar.commit(t1)
which doesn't do anything. which doesn't do anything.
...@@ -795,7 +795,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort(): ...@@ -795,7 +795,7 @@ def test_tpc_abort_w_subtransactions_featuring_subtransaction_abort():
>>> jar.tpc_abort(t1) >>> jar.tpc_abort(t1)
An the changes are undone: An the changes are undone:
>>> dm.state, dm.delta >>> dm.state, dm.delta
(0, 0) (0, 0)
>>> dm.prepared >>> dm.prepared
......
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
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7