An error occurred fetching the project authors.
- 29 Jun, 2004 1 commit
-
-
Tim Peters authored
-
- 07 Jun, 2004 1 commit
-
-
Tim Peters authored
-
- 02 Jun, 2004 1 commit
-
-
Jim Fulton authored
-
- 14 May, 2004 1 commit
-
-
Tim Peters authored
-
- 16 Apr, 2004 2 commits
-
-
Jeremy Hylton authored
-
Jeremy Hylton authored
-
- 06 Apr, 2004 2 commits
-
-
Tim Peters authored
an object as a non-negative integer. Code trying to pass addresses to an %x format uses positive_id(), and this avoids a Python FutureWarning about applying %x to negative ints. The primary difference between this and the last stab is that positive_id() should work OK on 64-bit boxes too. What we really want here is C's %p format code, but in Python we can't even reliably know the width of native addresses.
-
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 2 commits
-
-
Tim Peters authored
testExceptionInTpcAbort(). The cause is clear now, but a solution isn't; an exception in tpc_abort is nasty.
-
Tim Peters authored
(something's not right in this test).
-
- 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.
-
- 27 Feb, 2004 1 commit
-
-
Martijn Faassen authored
-
- 19 Feb, 2004 1 commit
-
-
Jeremy Hylton authored
Add support for persistent weak references. The implementation is in pure Python right now; coptimizations.c was disabled. We need to restore the C code before going to beta. The persistent reference format has evolved a little, but the code on the branch doesn't document it. The ref is usually a an oid-class pair, where the class is an actual class object. It can also be a list, for weak references, or a bare oid. Add support for data managers written against the ZODB4 transaction API. The transaction implementation provides an adapter between the two interfaces. There's a substantial doctest test suite for this feature. Add add() method to Connection to explicitly add an object and get it an assigned _p_oid. It's possible to add an unconnected object; this isn't recommended, because it will be lost at pack time.
-
- 24 Dec, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 28 Nov, 2003 1 commit
-
-
Jim Fulton authored
-
- 18 Nov, 2003 1 commit
-
-
Tres Seaver authored
-
- 05 Oct, 2003 1 commit
-
-
Chris McDonough authored
-
- 02 Oct, 2003 1 commit
-
-
Jeremy Hylton authored
-
- 27 Jan, 2003 1 commit
-
-
Barry Warsaw authored
we should eventually hook this into ZConfig.
-
- 15 Aug, 2002 1 commit
-
-
Jeremy Hylton authored
The order in which the tpc_finish() method of the jars is called is dependent on the order in which objects are returned from dict.values(). There is no way to write a test that works on all platforms that produces a consistent result in dict.values(), so stop trying. Instead, have the jars explicitly coordinate their tpc_finish() methods so that the first call always succeeds and the second call always fails.
-
- 14 Aug, 2002 2 commits
-
-
Martijn Pieters authored
-
Jeremy Hylton authored
and remove testExceptionInTpcFinish() and BUGtestExceptionInSubTpcBegin(). The tpc_finish test removed duplicated the logic of "hoser stoppage," while the BUGtest was never executed. The testHoserStoppage() test used to depend on the order of objects in a dict's values() list. This order was unpredictable and caused intermittent failures. Make two changes to work around this: 1) Mark the non-error object as modified first, since this seems to get values() in a good order. 2) Retry the test with 2 randomly selected objects until it passes, but fail after 10 tries.
-
- 12 Aug, 2002 1 commit
-
-
Jeremy Hylton authored
The HoserStoppage and ExceptionInTpcFinish were failing intermittently on Windows. I assume the problem is that a single error in tpc_finish() can be recovered from iff the error is for the first jar. I assume that most of the time the error occurred after some other jar had committed. Fixed the test by causing two different jars to fail.
-
- 15 Apr, 2002 1 commit
-
-
Jeremy Hylton authored
Also, reformat a test in testTransaction.
-
- 12 Apr, 2002 1 commit
-
-
Jeremy Hylton authored
including some use of assert/fail methods instead of assert stmt.
-
- 12 Mar, 2002 2 commits
-
-
Kapil Thangavelu authored
don't pass, and have been prefixed by 'BUG'
-
Kapil Thangavelu authored
-
- 21 Jan, 2002 1 commit
-
-
Jeremy Hylton authored
-
- 07 Aug, 2001 1 commit
-
-
Jeremy Hylton authored
-
- 10 May, 2001 1 commit
-
-
Jeremy Hylton authored
sub-transactions XXX Need to apply effbot's lambda-refactoring pattern
-