An error occurred fetching the project authors.
- 20 May, 2005 2 commits
-
-
Tim Peters authored
-
Tim Peters authored
Use ZConfig's new socket address types appropriately. These config file keys changed: section key was is ------- --------------- -------------- ------------------------- zeo address socket-address socket-binding-address zeo monitor-address socket-address socket-binding-address zeoclient server socket-address socket-connection-address
-
- 19 May, 2005 1 commit
-
-
Tim Peters authored
Collector 1788: runzeo fails in 2.8 A patch from Mark Hammond to repair a new Windows-specific gimmick in ZEOServer.setup_win32_signals().
-
- 13 May, 2005 1 commit
-
-
Tim Peters authored
-
- 12 May, 2005 1 commit
-
-
Tim Peters authored
undoInfo() and undoLog() almost always returned wrong # of results. Repaired, + new tests.
-
- 11 May, 2005 1 commit
-
-
Tim Peters authored
Combine the news items from the last 8 "internal releases" -- had become impossible to follow.
-
- 09 May, 2005 2 commits
-
-
Tim Peters authored
An internal 3.4a8 release, to test Zope2 with ZAapplication moved.
-
Tim Peters authored
ZApplication.py is moving to Zope trunk.
-
- 06 May, 2005 4 commits
-
-
Tim Peters authored
__call__() got broken about a year ago. There are no tests for this.
-
Tim Peters authored
Fix obscure bug. If a threaded transaction manager ever passed None to the Transaction constructor's `synchronizers` argument, then synchronizers registered later in the same transaction were invisible to the transaction, and so their afterCompletion() methods wouldn't get called when the transaction ended.
-
Tim Peters authored
-
Tim Peters authored
ISynchronizer grows a newTransaction() method, called whenever TransactionManager.begin() is called. Connection implements that, and changes its ISynchronizer afterCompletion() method, to call sync() on its storage (if the storage has such a method), and to process invalidations in any case. The bottom line is that storage sync() will get done "by magic" now after top-level commit() and abort(), and after explicit TransactionManager.begin(). This should make it possible to deprecate Connection.sync(), although I'm not doing that yet. Made a small but meaningful start by purging many sync() calls from some of the nastiest ZEO tests -- and they still work fine.
-
- 02 May, 2005 1 commit
-
-
Tim Peters authored
Port from ZODB 3.2. Added new test checkSubtxnCommitDoesntGetInvalidations to verify that a longstanding bug in subtransaction commit is repaired. Jim (Fulton) discovered this in ZODB 3.4's code, while implementing savepoint/rollback. Same bugs had been there at least since ZODB 3.1. Also added news about the bug.
-
- 26 Apr, 2005 2 commits
-
-
Tim Peters authored
Repaired NEWS format; predicted the next release will be 3.4b1.
-
Florent Guillaume authored
A ``getBeforeCommitHooks()`` method has been added to Transaction. It returns an iterable producing the registered beforeCommit hooks.
-
- 25 Apr, 2005 1 commit
-
-
Tim Peters authored
Original checkin comments follow: r30168 | tim_one | 2005-04-25 14:17:37 -0400 (Mon, 25 Apr 2005) | 2 lines M /ZODB/branches/3.4/NEWS.txt ... An internal 3.4a5 release, to incorporate savepoint fixes. r30165 | jim | 2005-04-25 12:29:28 -0400 (Mon, 25 Apr 2005) | 11 lines M /ZODB/branches/3.4/src/transaction/_transaction.py M /ZODB/branches/3.4/src/transaction/savepoint.txt M /ZODB/branches/3.4/src/transaction/tests/test_savepoint.py Fixed a bug in savepoint rollback. It's not enough to rollback just the savepoint being rolled back because later savepoints might involved data managers that hadn't joined when the savepoint being rolled back was created. Now, when a data manager joins and we have savepoints, we create a data manager savepoint for the new data manager and add the datamanager savepoint to all previous transaction savepoints. Note that this data manager savepoint can be a special savepoint that just calls abort on the data manager when it is rolled back. r30164 | tim_one | 2005-04-25 11:16:20 -0400 (Mon, 25 Apr 2005) | 2 lines r30163 | tim_one | 2005-04-25 11:08:37 -0400 (Mon, 25 Apr 2005) | 2 lines r30162 | tim_one | 2005-04-25 11:06:51 -0400 (Mon, 25 Apr 2005) | 2 lines M /ZODB/branches/3.4/src/transaction/interfaces.py Grammar, spelling, English. Close unterminated sentences. Trim trailing whitespace. r30161 | jim | 2005-04-25 10:51:16 -0400 (Mon, 25 Apr 2005) | 10 lines M /ZODB/branches/3.4/src/transaction/interfaces.py Removed a "self" argument. self is normally not shown in interfaces. Removed the freeme argument. This argument is part of the implementation, not the public interface. Removed the subtransaction argument. Although it is still supported, it isn't part of the pblic interface. Added missing documentation of the savepoint method. r30160 | jim | 2005-04-25 10:41:08 -0400 (Mon, 25 Apr 2005) | 2 lines M /ZODB/branches/3.4/src/transaction/interfaces.py Removed some stale discussion of subtransactions. r30147 | jim | 2005-04-24 11:26:39 -0400 (Sun, 24 Apr 2005) | 7 lines M /ZODB/branches/3.4/src/transaction/_transaction.py M /ZODB/branches/3.4/src/transaction/savepoint.txt Make transactions uncommitable if savepoint rollback fails. Added demonstration of transaction non-commitability after savepoint or savepoint rollback failure. Updated "previous commit failed" error to "previous operation failed". r30146 | jim | 2005-04-24 11:26:37 -0400 (Sun, 24 Apr 2005) | 5 lines M /ZODB/branches/3.4/src/ZODB/Connection.py M /ZODB/branches/3.4/src/transaction/interfaces.py M /ZODB/branches/3.4/src/transaction/tests/savepointsample.py Refined interfaces to distinguish between data-manager savepoints and transaction savepoints. Updated some interface declarations. r30145 | jim | 2005-04-24 10:48:15 -0400 (Sun, 24 Apr 2005) | 2 lines M /ZODB/branches/3.4/src/ZODB/tests/testConnectionSavepoint.py added explanatory text r30144 | jim | 2005-04-24 10:35:49 -0400 (Sun, 24 Apr 2005) | 2 lines Changed paths: M /ZODB/branches/3.4/NEWS.txt Updated to reflect savepoints.
-
- 23 Apr, 2005 1 commit
-
-
Tim Peters authored
ZEO version numbers the same (an auto-merge could do very little of this correctly!).
-
- 22 Apr, 2005 3 commits
-
-
Tim Peters authored
Port ZEO changes for Windows from ZODB 3.2. In addition, repaired the useless default logging in runzeo.py. Here's Sidnei's Zope 2.7 checkin comment: * Borrow Zope's 'Signal' mechanism for Windows, if available, to implement clean shutdown and log rotation handlers for Windows. * Back to creating a .PID for ZEO, so external programs that wish to set the 'signal' can get the PID and therefore derive the signal name. Currently only necessary on Windows but created on all platforms which implement os.getpid(), as long as the 'pid-filename' option is set, or the 'INSTANCE_HOME' environment variable can be found.
-
Tim Peters authored
Port from ZODB 3.2. DemoStorage: Added implementations for registerDB() and new_oid(). As Tres discovered the hard way, wrapping a ZEO client storage as a DemoStorage base storage yields insane behavior otherwise. BaseStorage.new_oid(): Rewrite to eliminate recursion, and hence also the need for the undocumented and irregular `last=` argument. Other: removed the `last=` argument to new_oid() every place that felt compelled to spread that insanity ;-). Seriously, it served no purpose at all elsewhere, and looks like people just cut 'n pasted in fear.
-
Tim Peters authored
Delayed news about old fsdump improvement.
-
- 13 Apr, 2005 1 commit
-
-
Tim Peters authored
-
- 07 Apr, 2005 1 commit
-
-
Tim Peters authored
Merge ZODB/branches/efge-beforeCommitHook. This is Florent Guillaume's branch, giving transaction objects a new beforeCommitHook() method, as proposed by Jim Fulton on zodb-dev. Some changes were made to the branch code (comments, more tests, more words in the docs).
-
- 05 Apr, 2005 1 commit
-
-
Tim Peters authored
Port from 3.3 branch. Port from Zope 2.7 branch. The various flavors of the ``check2ZODBThreads`` and ``check7ZODBThreads`` tests are much less likely to suffer sproadic failures now.
-
- 03 Apr, 2005 1 commit
-
-
Tim Peters authored
-
- 01 Apr, 2005 6 commits
-
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
This is news about ZEO protocol changes. The promised update of README.txt will have to be rewritten from scratch for 3.4 (the new text in 3.3's README.txt isn't quite right for the 3.4 release).
-
- 28 Mar, 2005 1 commit
-
-
Tim Peters authored
Change default port # from 9999 to 8100, to match zope.conf (well, on Zope trunk anyway -- the ZEO client example appears to have gone missing from zope.conf on Zope3 trunk).
-
- 24 Mar, 2005 1 commit
-
-
Tim Peters authored
Collector #1734. Critical bug in BTree conflict resolution. Stop silent data loss in some BTree cases where a transaction adds a new key to a bucket while a concurrent transaction deletes all keys from the same bucket. Still needs porting to 3.2 line.
-
- 22 Mar, 2005 1 commit
-
-
Tim Peters authored
Various Zopes probably need changes too (to avoid the new deprecation warnings).
-
- 21 Mar, 2005 4 commits
-
-
Tim Peters authored
Jim (Fulton) points out that it's not entirely clear that the new format can't be read by older ZODBs, and Tim doesn't think it's worth the bother to find out for sure.
-
Tim Peters authored
Added news blurbs about fsIndex improvements, and about that .index files written by 3.4 won't be readable by earlier ZODBs.
-
Tim Peters authored
-
Tim Peters authored
-
- 20 Mar, 2005 2 commits
-
-
Chris McDonough authored
No commit message
-
Tim Peters authored
Document exclude{min,max}. The ZODB4 BTrees excludemin/excludemax arguments got implemented in 3.3, but the corresponding changes to the BTrees interface file got dropped on the floor.
-
- 14 Mar, 2005 1 commit
-
-
Tim Peters authored
Backward compatibility hack for ZODB.Persistent{List,Mapping}. Allow those old (ZODB 3.2) dotted paths to work again. Fallout: testPersistentMapping.py hasn't actually run anything for a long time, due to a mysterious "return None" at the start of its test_suite() function. Removed that. Then its checkNewPicklesAreSafe test failed. Spent 15 minutes on that, and gave up -- I'm still not even sure what it's _trying_ to test. Changed it to a TODO.
-