1. 26 Oct, 2004 2 commits
  2. 18 Oct, 2004 1 commit
  3. 15 Oct, 2004 2 commits
  4. 14 Oct, 2004 2 commits
  5. 12 Oct, 2004 4 commits
  6. 08 Oct, 2004 3 commits
  7. 05 Oct, 2004 1 commit
  8. 04 Oct, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27742 from 3.3 branch. · 8b3e8be0
      Tim Peters authored
      Use proto 1 pickles in ZEO/zrpc/Marshaller.encode().
      
      This rehabilitates the good part of Andreas's change; adds
      news; adds comments; and adds more comments about the
      sequence of undocumented cPickle gimmicks this relies on.
      8b3e8be0
  9. 30 Sep, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27723 from 3.3 branch. · 17570541
      Tim Peters authored
      Merge rev 27722 from Zope trunk.
      
      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.
      17570541
    • Tim Peters's avatar
      Merge rev 27717 from 3.3 branch. · 8a1a6c8d
      Tim Peters authored
      Merge rev 27712 from Zope trunk.
      
      Restore the Connection._opened attribute, actually used by
      DB.connectionDebugInfo().
      8a1a6c8d
  10. 29 Sep, 2004 2 commits
  11. 27 Sep, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27695 from 3.3 branch. · 057ac364
      Tim Peters authored
      Transaction.begin().
      
      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.
      057ac364
  12. 23 Sep, 2004 1 commit
  13. 17 Sep, 2004 4 commits
    • Tim Peters's avatar
      Merge rev 27621 from 3.3 branch. · 01d5b6c3
      Tim Peters authored
      Check in stuff mistakenly committed from the Zope trunk.
      
      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.
      01d5b6c3
    • Tim Peters's avatar
      7135a68c
    • Tim Peters's avatar
      40a41cf9
    • Tim Peters's avatar
      Merge rev 27557 from 3.3 branch. · ddfa17a2
      Tim Peters authored
      New test checkReadConflictErrorClearedDuringAbort().
      
      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.
      ddfa17a2
  14. 14 Sep, 2004 4 commits
    • Tim Peters's avatar
      Merge rev 27526 from 3.3 branch. · cd339ce8
      Tim Peters authored
      Act as if a 3.3c1 release were being made.  Maybe it will
      be.  Besides "the usual" release fiddling, repaired many
      out-of-date pieces of the ZODB programming guide; I'm sure
      many remain, though.
      cd339ce8
    • Tim Peters's avatar
      Merge rev 27524 from 3.3 branch. · 4f8b410a
      Tim Peters authored
      A test here didn't clean up after a failing commit().
      4f8b410a
    • Tim Peters's avatar
      Merge rev 27522 from 3.3 branch. · d7c99101
      Tim Peters authored
      Removed obsolete comment.
      d7c99101
    • Tim Peters's avatar
      Merge rev 27520 from 3.3 branch. · a3757926
      Tim Peters authored
      As discussed on zodb-dev, failing commit "sticks" now.
      
      After a commit fails (raises an exception), all subsequent attempts
      to commit, join, or register with the transaction now raise the new
      TransactionFailedError.  The failed transaction must be explicitly
      discarded now, via abort() on the transaction or begin() on its
      transaction manager.
      a3757926
  15. 10 Sep, 2004 1 commit
  16. 09 Sep, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27481 from 3.3 branch. · 343c2b08
      Tim Peters authored
      Forward port from Zope 2.7 branch.
      
      The ConflictError.get_{old,new}_serial() methods each did what the other
      was supposed to do.
      343c2b08
  17. 04 Sep, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27446 from 3.3 branch. · fcac19d9
      Tim Peters authored
      Port from Zope 2.7 branch.
      
      Collector #1488 (TemporaryStorage -- going backward in time).
      
      This confusion was really due to that the detail on a ConflictError
      exception didn't make sense.
      fcac19d9
  18. 31 Aug, 2004 3 commits
  19. 27 Aug, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27301 from 3.3 branch. · 84887168
      Tim Peters authored
      Raise ConnectionStateError if an attempt to close a connection
      is made while the connection has a pending subtransaction.
      84887168
  20. 26 Aug, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27279 from 3.3 branch. · 7f5c6b9d
      Tim Peters authored
      Transaction.begin() didn't do anything.
      
      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.
      7f5c6b9d
  21. 25 Aug, 2004 2 commits