1. 01 Apr, 2007 1 commit
  2. 28 Feb, 2007 3 commits
  3. 27 Feb, 2007 1 commit
  4. 26 Feb, 2007 1 commit
  5. 15 Feb, 2007 1 commit
  6. 06 Feb, 2007 2 commits
    • Gary Poster's avatar
      05cf02d4
    • Gary Poster's avatar
      revert revision 72313: · 7d9a9e50
      Gary Poster authored
        "add new 64-bit btree types (patch from Jim), merged from trunk"
      
      Even though, as noted in the history file, there is no official release
      of standalone ZODB 3.7, it corresponds with the release of Zope 3.3 and
      2.10 in 2006, and should be considered feature-frozen.  Jim has
      requested that these changes be reserved for the trunk (to be ZODB 3.8).
      
      A subsequent checkin will clarify the status of 3.7 in HISTORY.txt.
      
      7d9a9e50
  7. 01 Feb, 2007 1 commit
  8. 21 Nov, 2006 3 commits
  9. 16 Aug, 2006 1 commit
  10. 15 Aug, 2006 1 commit
  11. 14 Aug, 2006 1 commit
  12. 13 Aug, 2006 2 commits
  13. 27 Jul, 2006 1 commit
  14. 18 Jul, 2006 4 commits
  15. 16 Jun, 2006 1 commit
  16. 02 Jun, 2006 1 commit
  17. 08 May, 2006 1 commit
  18. 04 May, 2006 3 commits
  19. 17 Apr, 2006 1 commit
  20. 22 Mar, 2006 1 commit
  21. 02 Mar, 2006 1 commit
  22. 11 Feb, 2006 2 commits
  23. 03 Feb, 2006 1 commit
    • Shane Hathaway's avatar
      Fixed multiple undo in a transaction. · 9ce4c7fe
      Shane Hathaway authored
      For multiple undo to succeed, the undo operations have to be
      performed in a specific order.  The order was not being retained
      by ZODB and was instead semi-random (the order depended on the
      id() function.)  Now undo operations (as well as all
      ResourceManagers) are sorted by creation order.
      
      9ce4c7fe
  24. 23 Jan, 2006 1 commit
  25. 20 Jan, 2006 1 commit
  26. 05 Jan, 2006 1 commit
  27. 03 Jan, 2006 1 commit
  28. 02 Jan, 2006 1 commit
    • Tim Peters's avatar
      Merge rev 41063 from 3.6 branch. · 3e334b70
      Tim Peters authored
      _ConnectionPool._reduce_size():  when forgetting a Connection
      due to exceeding pool_size available connections, clear its
      cache right away.  Because such a connection can never be in
      the open state again, hanging on to resources in its cache is
      just wasteful.  This was reported as "a problem" on zodb-dev
      recently, although it's unclear how the poster got into a state
      where it mattered so much.
      3e334b70