An error occurred fetching the project authors.
- 10 Sep, 2004 1 commit
-
-
Tim Peters authored
Officially deprecate Transaction.begin().
-
- 26 Aug, 2004 1 commit
-
-
Tim Peters authored
Transaction.begin() didn't do anything. begin() is supposed to abort the current transaction, but Transaction.begin() did not. Calling begin() on a transaction *manager* worked fine, and is the intended way to do a begin() in 3.3. But calling begin() on a Transaction object is still very easy to do (e.g., the older get_transaction().begin() spelling still works), and shouldn't be a subtle disaster.
-
- 12 Aug, 2004 1 commit
-
-
Tim Peters authored
Please don't do that: ZODB changes need to be done in the ZODB project. Checkins to Zope3 have no effect on ZODB in reality. This includes: r26945 | jim | 2004-08-06 18:30:44 -0400 (Fri, 06 Aug 2004) | 6 lines M /Zope3/trunk/src/persistent/tests/test_persistent.py Updated to work with the versions of doctest from Python with versions greater than or equal to 2.3.0 and less than 2.4.0.a2 and with versions greater than 2.4.0a2. r26482 | srichter | 2004-07-13 13:07:03 -0400 (Tue, 13 Jul 2004) | 2 lines M /Zope3/trunk/src/transaction/__init__.py M /Zope3/trunk/src/transaction/_transaction.py M /Zope3/trunk/src/transaction/tests/test_transaction.py Converted XXX to TODO. r25953 | sidnei | 2004-06-23 13:14:20 -0400 (Wed, 23 Jun 2004) | 1 line M /Zope3/trunk/src/ZODB/interfaces.py M /Zope3/trunk/src/transaction/_transaction.py Add missing sortKey method to ZopeDBTransactionManager and DataManagerAdapter, and also add it to the interface. r25273 | philikon | 2004-06-06 04:43:57 -0400 (Sun, 06 Jun 2004) | 4 lines Changed paths: M /Zope3/trunk/src/BTrees M /Zope3/trunk/src/ZODB M /Zope3/trunk/src/persistent Ignore .so files. This fix should probably be merged to the original ZODB tree.
-
- 02 Jun, 2004 1 commit
-
-
Jim Fulton authored
-
- 16 Apr, 2004 1 commit
-
-
Tim Peters authored
essentially means a connection keep track of which objects from the connection are modified, instead of transactions keeping track of that. A good consequence hasn't yet been implemented: if a connection is closed with modifications still pending, we can detect that efficiently now, and complain.
-
- 14 Apr, 2004 1 commit
-
-
Jeremy Hylton authored
This changes the behavior slightly for invalidations. A Connection will receive invalidations even if it didn't have any modified objects in the transaction, e.g. db.undo() or a read-only transaction. For this to work, it assumes that the thread that called db.open() is the thread that is going to use the connection. If this isn't true, the synch argument to db.open() can be used to disable the new feature.
-
- 06 Apr, 2004 1 commit
-
-
Tim Peters authored
the former, remember it and raise it after calling _cleanup. If abort_sub() or tpc_abort() in _cleanup() also raise exceptions, log them but don't propagate them. This stops stray output produced by tests testExceptionInTpcAbort and testExceptionInSubAbortSub. Grrrrr: I haven't yet been able to figure out how to get logging to work in ZODB, so haven't yet been able to check that the new logging is reasonable.
-
- 02 Apr, 2004 1 commit
-
-
Tim Peters authored
testExceptionInTpcAbort(). The cause is clear now, but a solution isn't; an exception in tpc_abort is nasty.
-
- 01 Apr, 2004 1 commit
-
-
Jeremy Hylton authored
This branch introduces a new transaction API. The key features are: - top-level functions in transaction -- get(), commit(), abort() - explicit transaction manager objects - Transaction objects are used for exactly one transaction - support for transaction synchronizers The changes here are still provisional, but we want to get them off an obscure branch and onto the head for further development.
-