1. 11 Nov, 2004 5 commits
  2. 06 Nov, 2004 1 commit
  3. 05 Nov, 2004 1 commit
  4. 26 Oct, 2004 1 commit
  5. 18 Oct, 2004 1 commit
  6. 15 Oct, 2004 2 commits
  7. 14 Oct, 2004 2 commits
  8. 08 Oct, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27791 from trunk. · 68a22353
      Tim Peters authored
      Duplicate import removed.
      68a22353
    • Tim Peters's avatar
      Merge revs 27788 and 27795 from Zope trunk. · 605281d8
      Tim Peters authored
      See Collector #1350.
      
      ghostify() and unghostify() detect one form of thread insanity
      now.  In a debug build, they abort the process if it happens.
      In a release build, unghostify() raises SystemError, and
      ghostify() ignores it (ghostify() can't raise an exception).
      605281d8
  9. 05 Oct, 2004 1 commit
  10. 04 Oct, 2004 1 commit
  11. 30 Sep, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27222 from Zope trunk. · 16e43305
      Tim Peters authored
      Collector #1517: History tab for ZPT does not work
      
      FileStorage.history() was reading the user, description,
      and extension fields out of the object pickle, due to
      starting the read at a wrong location.
      16e43305
    • Tim Peters's avatar
      Merge rev 27712 from Zope trunk. · bc46ade8
      Tim Peters authored
      Restore the Connection._opened attribute, actually used by
      DB.connectionDebugInfo().
      bc46ade8
  12. 29 Sep, 2004 2 commits
  13. 27 Sep, 2004 1 commit
    • Tim Peters's avatar
      Transaction.begin(). · 47595ddf
      Tim Peters authored
      When raising DeprecationWarning, point the warning machinery at
      the caller, not at Transaction.begin() itself.  As is (voice
      of experience <wink>), these warnings are darned near useless to
      track down code that needs to be changed on Zope trunk.  With the
      change, the warnings point directly at the deprecated uses.
      47595ddf
  14. 23 Sep, 2004 1 commit
  15. 17 Sep, 2004 4 commits
    • Tim Peters's avatar
      Check in stuff mistakenly committed from the Zope trunk. · 54d6b5a3
      Tim Peters authored
      Rev 26842 changed cache-size parameters to type byte-size.
      That's a good change, but it was checked in from a wrong place
      (from the Zope trunk's copy of ZODB).  Since we want Zope 2.8 to
      be usable with ZODB 3.3 too, I need to slam this change into
      3.3 now.
      
      Alas, I don't understand how ZODB+ZEO got stitched into the
      Zope trunk (I do understand how it got stitched into the
      Zope3 trunk, and into the X3 branch), and it looks like that
      was left in a poor state.
      54d6b5a3
    • Tim Peters's avatar
      Repair a Trove line I just damaged. · 993d6c16
      Tim Peters authored
      993d6c16
    • Tim Peters's avatar
      Pretend 3.3 final is being released. · cb6f3dd5
      Tim Peters authored
      So that if Zope X3-3.0 final is released while I'm on vacation,
      it will have the right ZODB stuff in it (although I still need
      to stitch this in to the Zope 3 and X3 trees).
      cb6f3dd5
    • Tim Peters's avatar
      New test checkReadConflictErrorClearedDuringAbort(). · a1833cc9
      Tim Peters authored
      This confirms that 3.3 didn't have the 3.2.4c1 bug wherein
      an explict transaction abort() failed to clear Connections'
      memory of ReadConflictErrors.
      a1833cc9
  16. 14 Sep, 2004 4 commits
  17. 10 Sep, 2004 2 commits
  18. 09 Sep, 2004 1 commit
  19. 04 Sep, 2004 2 commits
  20. 31 Aug, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27375 from trunk. · d039df16
      Tim Peters authored
      Forward port from Zope 2.7 branch.
      
      _handle_independent():  Failed to record that a ReadConflictError
      was raised for an object with a _p_independent() method that
      returned false.
      d039df16
  21. 27 Aug, 2004 1 commit
  22. 26 Aug, 2004 1 commit
    • Tim Peters's avatar
      Transaction.begin() didn't do anything. · c9da918d
      Tim Peters authored
      begin() is supposed to abort the current transaction, but
      Transaction.begin() did not.  Calling begin() on a transaction
      *manager* worked fine, and is the intended way to do a begin()
      in 3.3.  But calling begin() on a Transaction object is still
      very easy to do (e.g., the older get_transaction().begin()
      spelling still works), and shouldn't be a subtle disaster.
      c9da918d
  23. 25 Aug, 2004 1 commit