1. 20 Sep, 2010 12 commits
    • Jim Fulton's avatar
      Bug fixed: · 8c10da5a
      Jim Fulton authored
       Process exits or database closes could cause ZEO caches to have
       incorrect data due to a problem in the way invalidations were processed.
      8c10da5a
    • Jim Fulton's avatar
      Bug fixed: · 8a150417
      Jim Fulton authored
      - Shutting down a process while committing a transaction could cause
        ZEO client caches to have invalid data.  This, in turn caused stale
        data to remain in the cache until it was updated.
      8a150417
    • Jim Fulton's avatar
      Bug fixed: · d5a9f2e9
      Jim Fulton authored
        When an integer too large to fit in a 32-bit integer was provided as
        a 32-bit-integer BTree key or value on 64-bit machines, an
        OverflowError was raised. Now a TypeError is raised.
      d5a9f2e9
    • Jim Fulton's avatar
      d1dc2637
    • Jim Fulton's avatar
      Use print to display tell output to avoid unimportant differences · f8775695
      Jim Fulton authored
      between logs and ints.
      f8775695
    • Jim Fulton's avatar
      Bug Fixed: · 1078ed5b
      Jim Fulton authored
      - Conflict errors didn't invalidate ZEO cache entries.
      1078ed5b
    • Jim Fulton's avatar
      Bugs fixes: · bc066b9a
      Jim Fulton authored
      - If a ZEO client process was restarted while invalidating a ZEO cache
        entry, the cache could be left in a stage when there is data marked
        current that should be invalidated, leading to persistent conflict
        errors.
      
      - Corrupted or invalid cache files prevented ZEO clients from
        starting. Now, bad cache files are moved aside.
      
      - Invalidations of object records in ZEO caches, where the
        invalidation transaction ids matched the cached transaction ids
        should have been ignored.
      bc066b9a
    • Jim Fulton's avatar
      Don't update the cache lastTid until we've invalidated a value (rather · 40bbc6b5
      Jim Fulton authored
      than before).  It's possible that process shutdown after updating
      lastTid but before invalidating the current record could explain some
      problems we've seen on restarts.
      
      (This change is made irrelevent by later changes.)
      40bbc6b5
    • Jim Fulton's avatar
      reintify on 32-bit systems · ee1a527a
      Jim Fulton authored
      ee1a527a
    • Jim Fulton's avatar
      Bug Fixed: · 9dd3b68c
      Jim Fulton authored
      - BTree sets and tree sets didn't correctly check values passed to
        update or to constructors, causing Python to exit under certain
        circumstances.
      9dd3b68c
    • Jim Fulton's avatar
      Bug Fixed · c7b7c0ee
      Jim Fulton authored
      - Updating blobs in save points could cause spurious "invalidations
        out of order" errors.  https://bugs.launchpad.net/zodb/+bug/509801
      
      (Thanks to Christian Zagrodnick for chasing this down.)
      c7b7c0ee
    • Jim Fulton's avatar
      Fixed bug: · ae1636e9
      Jim Fulton authored
      - BTree sets and tree sets didn't correctly check values passed to
        update or to constructors, causing Python to exit under certain
        circumstances.
      ae1636e9
  2. 21 Jun, 2010 1 commit
  3. 13 May, 2010 1 commit
  4. 27 Apr, 2010 1 commit
  5. 23 Apr, 2010 5 commits
  6. 21 Apr, 2010 3 commits
  7. 20 Apr, 2010 3 commits
  8. 23 Mar, 2010 2 commits
  9. 07 Mar, 2010 1 commit
  10. 20 Dec, 2009 1 commit
  11. 15 Dec, 2009 1 commit
  12. 14 Dec, 2009 5 commits
  13. 11 Dec, 2009 1 commit
  14. 03 Dec, 2009 2 commits
  15. 01 Dec, 2009 1 commit