1. 28 Mar, 2005 3 commits
    • Tim Peters's avatar
      checkTimeoutProvokingConflicts: try to fix rare failures. · 4659d8eb
      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.
      4659d8eb
    • Tim Peters's avatar
      Merge rev 29706 from 3.3 branch. · a7a9c6a2
      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).
      a7a9c6a2
    • Tim Peters's avatar
      Merge rev 29705 from 3.3 branch. · efc49694
      Tim Peters authored
      s/zeo/ZEO/ in logger name, to match other ZEO logger names.
      efc49694
  2. 24 Mar, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29668 from 3.3 branch. · bb3d142c
      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.
      bb3d142c
  3. 22 Mar, 2005 2 commits
  4. 21 Mar, 2005 13 commits
  5. 20 Mar, 2005 5 commits
  6. 17 Mar, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29532 from 3.3 branch. · 8218f4bb
      Tim Peters authored
      Merge checkin made from a wrong project:
      
      r29511 | gotcha | 2005-03-16 11:01:21 -0500 (Wed, 16 Mar 2005) | 1 line
      Changed paths:
         M /Zope/trunk/utilities/ZODBTools/zodbload.py
      
      port features from 2.7
      8218f4bb
  7. 14 Mar, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29467 from 3.3 branch. · d7276762
      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.
      d7276762
  8. 11 Mar, 2005 3 commits
  9. 07 Mar, 2005 1 commit
  10. 03 Mar, 2005 1 commit
    • Tim Peters's avatar
      Merge ZODB trunk changes checked in from a wrong project. · 7c665d9a
      Tim Peters authored
      r29290 | frerich | 2005-02-24 17:36:00 -0500 (Thu, 24 Feb 2005)
      Changed paths:
         M /Zope3/trunk/src/ZODB/tests/dbopen.txt
         ...
         minor editing
      
      r29247 | gintautasm | 2005-02-22 06:40:26 -0500 (Tue, 22 Feb 2005)
      Changed paths:
         M /Zope3/trunk/src/BTrees/Interfaces.py
         ...
         More minor nitpicks.  This should be the last one.
      
      7c665d9a
  11. 02 Mar, 2005 3 commits
  12. 01 Mar, 2005 1 commit
  13. 28 Feb, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29350 from ZODB 3.3 branch. · e6f505df
      Tim Peters authored
      Port from ZODB 3.2.
      
      Change FileStorage .restore() and .store() to update max oid in use.
      
      This is the last of the checkins to fix critical bugs involving rare cases
      where a FileStorage could end up reusing old oids for new objects.
      e6f505df
  14. 25 Feb, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29302 from 3.3 branch. · ed9ebe85
      Tim Peters authored
      Port from ZODB 3.2.
      
      Stop believing the maximum oid cached in a FileStorage's .index file.
      
      This is a critical bugfix, although the problems it addresses are
      (a) rare; and, (b) not entirely fixed yet (more checkins to come).
      
      The true max oid is found efficiently now by exploiting the recently-added
      fsIndex.maxKey() method (which was, of course, added for this purpose).
      
      Also fix that the .index file could get updated on disk when the
      FileStorage was opened in read-only mode.  The code was trying to prevent
      this, but missed the most obvious rewrite path.
      
      Incidentally improved many obsolete and/or incorrect comments.
      ed9ebe85
  15. 24 Feb, 2005 2 commits
    • Tim Peters's avatar
      Merge rev 29291 from ZODB 3.3 branch. · f82de536
      Tim Peters authored
      Port from ZODB 3.2.
      
      Give fsIndex an efficient maxKey() implementation.
      
      This will (in a later checkin) be used to give FileStorage an "obviously
      correct" way to determine the largest oid used in an .fs.index file.
      f82de536
    • Tim Peters's avatar
      Merge rev 29286 from ZODB 3.3 branch. · f2a5c8f4
      Tim Peters authored
      Port from ZODB 3.2.
      
      Note that cPickleCache.c must be recompiled else the new test will fail.
      
      Change the exception raised when an attempt is made to add two objects to
      the cache with the same oid.  The former messsage didn't make sense.
      
      Add a test to verify that this exception does get raised, and that the
      message given is the intended one.
      
      This is the first of a series of checkins, to fix critical bugs where
      ZODB can in fact raise this exception in rare, but normal, use cases.
      f2a5c8f4
  16. 17 Feb, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 29194 from 3.3 branch. · 138bb41f
      Tim Peters authored
      setUp():  Use a much smaller (than default) ZEO client cache.
      
      The current default is 200MB, and at least testSerialization reads
      the entire cache file into one giant string.  That grossly boosts
      the process highwater mark when running the tests.  Windows reclaims
      the memory after, but other platforms may not.
      
      Cool:  testSerialization was one of the slowest tests before, but
      is 100x faster now.
      138bb41f