1. 31 May, 2002 3 commits
  2. 30 May, 2002 7 commits
  3. 28 May, 2002 1 commit
  4. 25 May, 2002 1 commit
  5. 24 May, 2002 1 commit
  6. 23 May, 2002 2 commits
  7. 16 May, 2002 1 commit
    • Barry Warsaw's avatar
      checkTwoArgBegin(): Change the explicit tid that gets stored so that · 8b986684
      Barry Warsaw authored
      the Standby storage version of the test has a hope of succeeding.
      That storage ignores non-sensically out-of-sequence tids so as written
      this test wouldn't have passed until after 3220-07-29 10:18:09.882353
      <methuselah wink>.
      
      We'll use a tid that we know is earlier than now.
      8b986684
  8. 13 May, 2002 1 commit
  9. 09 May, 2002 2 commits
  10. 06 May, 2002 1 commit
  11. 03 May, 2002 4 commits
  12. 02 May, 2002 2 commits
  13. 29 Apr, 2002 2 commits
  14. 23 Apr, 2002 1 commit
  15. 22 Apr, 2002 3 commits
  16. 18 Apr, 2002 3 commits
  17. 17 Apr, 2002 1 commit
  18. 16 Apr, 2002 1 commit
  19. 15 Apr, 2002 3 commits
    • Jeremy Hylton's avatar
      Turn off MUCH_RING_CHECKING. · 1cb93e7d
      Jeremy Hylton authored
      I think it's safe to run this code without extra checking.
      1cb93e7d
    • Jeremy Hylton's avatar
      Add a bunch more tests of the LRU cache mechanism and of DB methods. · 43fa28e3
      Jeremy Hylton authored
      Also, reformat a test in testTransaction.
      43fa28e3
    • Jeremy Hylton's avatar
      Remove the cache_deactivate_after argument from the cPickleCache · 8007802d
      Jeremy Hylton authored
      constructor, since it is ignored and there is no current plan to
      support two caches with almost-but-not-quite-the-same arguments.
      
      This change has effects in many files.  The Connection and DB don't
      pass this argument and don't bother setting it explicitly when it is
      reset via DB APIs like setCacheDeactivateAfter().  XXX These APIs
      remain, since existing code may depend on them, but they have no
      effect.
      
      New policy in cPersistence.c: A Persistent object can't have its
      _p_jar set or deleted once it is in a cache.  Persistent already
      implemented this policy for _p_oid; it seems safer to do the same for
      the jar.
      
      Add ringlen() method to cache objects (implemented as cc_ringlen).
      This returns the length of the doubly linked list of non-ghost
      objects.  Same as len(cache.lru_items()), but more efficient.  Only
      used for testing at the moment.
      
      In ring_corrupt(), don't raise a new exception if one has already been
      set.  The old behavior masked useful information about the original
      error / traceback.
      8007802d