1. 06 May, 2005 6 commits
    • Tim Peters's avatar
      Fixed some incorrect comments. · 4b10c219
      Tim Peters authored
      4b10c219
    • Tim Peters's avatar
      Make an internal 3.4a7 release. · d7a582f9
      Tim Peters authored
      d7a582f9
    • Tim Peters's avatar
      Fix obscure bug. · 09728090
      Tim Peters authored
      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.
      09728090
    • Tim Peters's avatar
      2b790fba
    • Tim Peters's avatar
      Make an internal 3.4a6 release, primarily for Zope 2.8. · 9b42a5e0
      Tim Peters authored
      This is effectively a beta release, but I don't want to
      take the time to do a full-blown release right now.
      9b42a5e0
    • Tim Peters's avatar
      ISynchronizer grows a newTransaction() method, called · 476e7bd8
      Tim Peters authored
      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.
      476e7bd8
  2. 03 May, 2005 1 commit
    • Tim Peters's avatar
      Partial savepoint review. · e3f4fb77
      Tim Peters authored
      Added more comments.  Changed some comments to English.
      Renamed some attributes and methods for clarity.
      Switched to using a Python WeakKeyDictionary instead of
      rolling our own out of a Python dict and raw weakrefs.
      e3f4fb77
  3. 02 May, 2005 1 commit
    • Tim Peters's avatar
      Port from ZODB 3.2. · 4fee6a4b
      Tim Peters authored
      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.
      4fee6a4b
  4. 28 Apr, 2005 1 commit
  5. 27 Apr, 2005 2 commits
    • Jim Fulton's avatar
      Fixed stupid bug. · 3ddf5afa
      Jim Fulton authored
      3ddf5afa
    • Jim Fulton's avatar
      Changed the strategy for managing savepoints. The requirements · f9de1eed
      Jim Fulton authored
      for savepoint management are:
      
      - All savepoints for a transaction should be invalidated when the
        transaction commits or aborts
      
      - If a savepoint is rolled back, then all savepoints after it within 
        a transaction must be invalidated.
      
      We previously implemented these requirements by organizing transaction
      savepoints into a doubly linked list.  This was overkill.  We didn't
      have need for such fine-grained ordering.  This strategy had the
      disadvantage that it kept all savepoints around until the transaction
      ended.  Savepoints could be expensive to keep and it's possible that
      some applications could keep a lot of them.
      
      The new stragey is to:
      
      - Keep weak references to savepoints.  We can forget about savepoints
        that the application isn't using.  Any resources used by these
        savepoints can be freed.
      
      (We have to keep a strong reference to the last savepoint used for
        a subtransaction.)
      
      - We assign indexes to savepoints within a transaction.  When a
        savepoint is rolled back, in addition to invalidating that
        savepoint, we also invalidate savepoints with a higher index.
      
      A side effect of this change is that code using the savepoint API
      should interfere less with code using subtransactions.  Of course, we
      really need to phase out code that uses subtransactions.
      
      It is likely that we can leverage this change in strategy to speed
      creation of ZODB connection savepoints.  Creating a ZODB connection
      savepoint now requires copying the savepoint storage index.  This
      index could become large.  If applications aren't holding on to old
      savepoints, then it is possible that we could avoid this copy.
      f9de1eed
  6. 26 Apr, 2005 3 commits
  7. 25 Apr, 2005 8 commits
  8. 24 Apr, 2005 9 commits
  9. 23 Apr, 2005 1 commit
  10. 22 Apr, 2005 3 commits
    • Tim Peters's avatar
      Port ZEO changes for Windows from ZODB 3.2. · 555f6432
      Tim Peters authored
      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.
      555f6432
    • Tim Peters's avatar
      Port from ZODB 3.2. · 056eaa64
      Tim Peters authored
      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.
      056eaa64
    • Tim Peters's avatar
      Delayed news about old fsdump improvement. · 1784f286
      Tim Peters authored
      1784f286
  11. 14 Apr, 2005 1 commit
  12. 13 Apr, 2005 3 commits
  13. 10 Apr, 2005 1 commit
    • Tim Peters's avatar
      test_cache(): Muck with Python's warnings module. · 43ebe4b6
      Tim Peters authored
      The test didn't work if run more than once (e.g., via Zope3's
       test.py's "-N <n>" argument, or via ZODB's test.py's "-L"
      argument), because the warnings module suppresses warnings
      after the first a single line.  Made the warnings module
      report repeats of DeprecationWarnings for the duration of
      the test.
      43ebe4b6