An error occurred fetching the project authors.
  1. 14 Jul, 2005 3 commits
  2. 12 Jul, 2005 2 commits
  3. 11 Jul, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 33273 from 3.4 branch. · ce0290a6
      Tim Peters authored
      Merge tim-savepoint branch.
      
      Allow rollback to a given savepoint multiple times.
      
      transaction/_transaction.py
          _remove_and_invalidate_after():  Don't remove the
          argument savepoint from the savepoint stack anymore.
      
          abort():  abort(True) relied on the subtxn savepoint
          being invalidated as a side effect of rolling back
          to it.  Invalidate it explicitly now.
      
          Savepoint.rollback():  Don't invalidate self.
      
      ZODB/Connection.py
          Connection._rollback():  Pass a temp container to
          _cache.invalidate(), because that method clears the
          container as a side effect.  Clearing the index
          in a savepoint was a disaster if the savepoint was
          used again.
      
          TmpStore.reset():  Make a copy of the argument index.
          An alternative would be to make all callers make
          copies, but the only caller now thinks of its `state`
          argument as being opaque.
      
      transaction/savepoint.txt
      ZODB/tests/{testSubTransaction.py, testConnectionSavepoint.txt}
          Test the new semantics, and beef up the tests.
      
      transaction/tests/savepointsample.py
          _rollback_savepoint():  Needed to copy the data.
      ce0290a6
  4. 08 Jul, 2005 1 commit
  5. 05 Jul, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 31010 from 3.4 branch. · 729faf25
      Tim Peters authored
      Collector 1831.
      
      The BTree minKey() and maxKey() methods gave a misleading message if no key
      satisfying the constraints existed in a non-empty tree.
      729faf25
  6. 02 Jul, 2005 1 commit
  7. 01 Jul, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30976 from 3.4 branch. · ee9d1302
      Tim Peters authored
      Collector 1829.
      
      Clarified that the ``minKey()`` and ``maxKey()`` methods raise an exception
      if no key exists satsifying the constraints.
      
      Also improved the English in other interface docstrings.
      ee9d1302
  8. 29 Jun, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30944 from 3.4 branch. · 45814f90
      Tim Peters authored
      Collector 1822.
      
      Make undo{Log,Info} arguments act like Python slice indices when
      both are non-negative.  The code used to do that before ZODB 3.4a9,
      but changed to match ZODB's UML documentation.  Alas, some
      (untested) code in Zope relied on the actual behavior (see the
      collector report).  Changed code, docs, and tests to bless the
      old behavior in these cases.
      
      DemoStorage.UndoLog:  this was wrong in several ways.  I'm still
      unsure about why it skips "packed" transactions.  That doesn't seem
      right, but I don't have time to wonder about that now.
      45814f90
  9. 27 Jun, 2005 1 commit
  10. 22 Jun, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30894 from 3.4 branch. · c43d7912
      Tim Peters authored
      Largely rewritten.
      
      remove_loop_callback():  There were two definitions of this function.
      Deleted one, changed the other to use enumerate().
      
      poll():  This was trying to repair a bug in Python 2.2's asyncore.poll().
      2.2 is no longer supported, so removed this poll().
      
      _start_loop(), _stop_loop():  Removed; functionality folded into
      reworked loop().
      
      loop():  The signature of asyncore.loop() changed in 2.4, but this
      still had "the old" signature.  Instead of sniffing the signature
      of the Python in use, this does a saner thing:  the original
      asyncore.loop is captured, and called from the body of this loop().
      That way, (A) we don't care what asyncore.loop's signature is; and,
      (B) we still call the original Python code, so debugging prints and
      breakpoints (etc) stuffed into Python's asyncore no longer "vanish
      by magic" when ZEO is used.
      c43d7912
  11. 17 Jun, 2005 1 commit
  12. 16 Jun, 2005 2 commits
  13. 14 Jun, 2005 1 commit
  14. 10 Jun, 2005 1 commit
  15. 06 Jun, 2005 2 commits
    • Tim Peters's avatar
      Merge news from 3.4c2. · d67e1854
      Tim Peters authored
      d67e1854
    • Tim Peters's avatar
      Mrege rev 30658 from 3.4 branch. · 4f144a34
      Tim Peters authored
      checkCrossDBInvalidations:  make this willing to wait longer in all,
      and increase the sleep time per failing loop iteration.  The hope is
      this will allow the test to pass on slower and/or "too busy" machines.
      I can't test that, though, since I couldn't get the test to fail at
      all on a Windows or a Linux box.
      4f144a34
  16. 03 Jun, 2005 1 commit
  17. 02 Jun, 2005 4 commits
  18. 27 May, 2005 2 commits
  19. 26 May, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30518 from 3.4 branch. · 5c34be65
      Tim Peters authored
      Change test.py to use zope.testing.testrunner, and update the
      latter to Jim's development version.  Hardest part turned out
      to be teaching ZODB's setup.py how to "build" this version of
      zope.testing (it has a lot of packages in a test directory,
      where the latter is not itself a package).
      
      Incidentally repaired an oversight in building zope.interface
      too.
      5c34be65
  20. 20 May, 2005 2 commits
    • Tim Peters's avatar
      Merge 3.4b1 news. · 6d35ea52
      Tim Peters authored
      6d35ea52
    • Tim Peters's avatar
      Merge rev 30437 from 3.4 branch. · 6d491ddb
      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
      6d491ddb
  21. 19 May, 2005 1 commit
    • Tim Peters's avatar
      Merge rev 30422 from 3.4 branch. · 924ec78e
      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().
      924ec78e
  22. 13 May, 2005 1 commit
  23. 12 May, 2005 1 commit
  24. 11 May, 2005 1 commit
  25. 09 May, 2005 2 commits
  26. 06 May, 2005 4 commits
    • Tim Peters's avatar
      Merge rev 30291 from 3.4 branch. · 3416d261
      Tim Peters authored
      __call__() got broken about a year ago.
      
      There are no tests for this.
      3416d261
    • Tim Peters's avatar
      Merge rev 30279 from 3.4 branch. · 11a9a4c2
      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.
      11a9a4c2
    • Tim Peters's avatar
      Merge 3.4a6 news. · a9736b15
      Tim Peters authored
      a9736b15
    • Tim Peters's avatar
      Merge rev 30255 from 3.4 branch. · 7db4484c
      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.
      7db4484c