1. 14 Sep, 2004 4 commits
    • Tim Peters's avatar
      Merge rev 27522 from 3.3 branch. · 294c2342
      Tim Peters authored
      Removed obsolete comment.
      294c2342
    • Tim Peters's avatar
      Removed obsolete comment. · 9214c90f
      Tim Peters authored
      9214c90f
    • Tim Peters's avatar
      Merge rev 27520 from 3.3 branch. · fe565385
      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.
      fe565385
    • Tim Peters's avatar
      As discussed on zodb-dev, failing commit "sticks" now. · 85aaf132
      Tim Peters authored
      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.
      85aaf132
  2. 10 Sep, 2004 4 commits
  3. 09 Sep, 2004 2 commits
  4. 04 Sep, 2004 3 commits
  5. 31 Aug, 2004 5 commits
  6. 27 Aug, 2004 2 commits
  7. 26 Aug, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27279 from 3.3 branch. · a1c7a05f
      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.
      a1c7a05f
    • Tim Peters's avatar
      Transaction.begin() didn't do anything. · b4731cf6
      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.
      b4731cf6
  8. 25 Aug, 2004 3 commits
  9. 23 Aug, 2004 3 commits
  10. 21 Aug, 2004 3 commits
  11. 20 Aug, 2004 1 commit
  12. 19 Aug, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27186 from trunk. · 40d192d9
      Tim Peters authored
      FileIterator.next():  the code for reading the user, description,
      and extension fields from a transaction was fatally confused,
      usually reading them out of the object pickle by mistake.  This
      caused several tools to display binary gibberish.
      40d192d9
    • Tim Peters's avatar
      FileIterator.next(): the code for reading the user, description, · 2a496112
      Tim Peters authored
      and extension fields from a transaction was fatally confused,
      usually reading them out of the object pickle by mistake.  This
      caused several tools to display binary gibberish.
      2a496112
  13. 18 Aug, 2004 2 commits
    • Tim Peters's avatar
      Merge rev 27179 from 3.3 branch. · 5aeb9653
      Tim Peters authored
      Forward port from Zope 2.7 branch.
      
      analyze_rec():  This produced spurious "len of unsized object" messages
      when a data record had a backpointer instead of a pickle.  Repaired.
      
      analyze(), analyze_trans():  Simplified overly elaborate iteration code.
      5aeb9653
    • Tim Peters's avatar
      Forward port from Zope 2.7 branch. · 3d5bb8a7
      Tim Peters authored
      analyze_rec():  This produced spurious "len of unsized object" messages
      when a data record had a backpointer instead of a pickle.  Repaired.
      
      analyze(), analyze_trans():  Simplified overly elaborate iteration code.
      3d5bb8a7
  14. 17 Aug, 2004 4 commits