- 03 Apr, 2005 3 commits
-
-
Tim Peters authored
-
Tim Peters authored
modifiedInVersion: remove set_trace() added during ZODB sprint.
-
Tim Peters authored
checkOldStyleRoot: Can't work in Zope3. The Persistence module no longer exists in Zope3's idea of what ZODB is, but this test relies on it. Make it tolerate the absence of Persistence.
-
- 01 Apr, 2005 10 commits
-
-
Fred Drake authored
-
Fred Drake authored
-
Fred Drake authored
-
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).
-
Tim Peters authored
Rewrite ZEO protocol negotiation. 3.3 should have bumped the ZEO protocol number (new methods were added for MVCC support), but didn't. Untangling this is a mess.
-
- 31 Mar, 2005 1 commit
-
-
Tim Peters authored
the most common cases (commit() and abort()) -- it's not really obvious that shortcut spelling exist for those.
-
- 30 Mar, 2005 2 commits
-
-
Tim Peters authored
Merge checkin made from a wrong project. Believe it or not, ZopeUndo is ZEO code, not Zope code. r29726 | slinkp | 2005-03-30 02:11:22 -0500 (Wed, 30 Mar 2005) | 3 lines Changed paths: M /Zope/trunk/lib/python/ZopeUndo/Prefix.py M /Zope/trunk/lib/python/ZopeUndo/tests/testPrefix.py Merged slinkp_1726_zopeundo: avoid showing undo transactions in the wrong folder.
-
Jim Fulton authored
-
- 28 Mar, 2005 3 commits
-
-
Tim Peters authored
This always slept for 3 seconds, waiting for the storage to disconnect. This loses on two counts: 1. Since the timeout is set to 1 second, it typically sleeps longer than necessary. 2. Since there's no predicting thread and process scheduling, 3 seconds isn't always long enough, and rare failures have been reported against this test. Instead we do a polling loop now. This typically succeeds in a little more than a second, speeding the normal case. The loop will continue trying for up to a minute if not.
-
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).
-
Tim Peters authored
s/zeo/ZEO/ in logger name, to match other ZEO logger names.
-
- 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 2 commits
-
-
Tim Peters authored
Various Zopes probably need changes too (to avoid the new deprecation warnings).
-
Tim Peters authored
-
- 21 Mar, 2005 13 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
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
-
Tim Peters authored
test.py ran these tests ran after "setup build_ext -i", but not after "setup build". Repaired by teaching setup.py to copy more stuff out of the relevant directories.
-
Tim Peters authored
There's a mystery: the tests for it appear to run after "build_ext -i", but not after "build". But that appears to be true for the long-stitched-in zope.interface too.
-
Tim Peters authored
-
Tim Peters authored
This introduces a "multi-database" concept (a simplification of Jim's Wiki proposal), and adds many interface definitions. Work done during the PyCon 2005 ZODB sprint, by Christian Theune, Jim Fulton and Tim Peters.
-
- 20 Mar, 2005 5 commits
-
-
Chris McDonough authored
-
Chris McDonough authored
-
Chris McDonough authored
No commit message
-
Chris McDonough authored
Add a record iteration protocol to FileStorage. You can use the record iterator to iterate over all current revisions of data pickles in the storage. In order to support calling via ZEO, we don't implement this as an actual iterator. An example of using the record iterator protocol is as follows: storage = FileStorage('anexisting.fs') next_oid = None while 1: oid, tid, data, next_oid = storage.record_iternext(next_oid) # do something with oid, tid and data if next_oid is None: break The behavior of the iteration protocol is now to iterate over all current records in the database in ascending oid order, although this is not a promise to do so in the future.
-
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.
-