1. 17 Sep, 2004 8 commits
    • Tim Peters's avatar
      Merge rev 27621 from 3.3 branch. · 5590ddae
      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.
      5590ddae
    • Tim Peters's avatar
      Check in stuff mistakenly committed from the Zope trunk. · fe2d10a6
      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.
      fe2d10a6
    • Tim Peters's avatar
      e08f0cdc
    • Tim Peters's avatar
      Repair a Trove line I just damaged. · fc42ffba
      Tim Peters authored
      fc42ffba
    • Tim Peters's avatar
      Pretend 3.3 final is being released. · bcc5b13e
      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).
      bcc5b13e
    • Tim Peters's avatar
      1c94750f
    • Tim Peters's avatar
      Merge rev 27557 from 3.3 branch. · 75f7ad02
      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.
      75f7ad02
    • Tim Peters's avatar
      New test checkReadConflictErrorClearedDuringAbort(). · ee6ca8ce
      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.
      ee6ca8ce
  2. 14 Sep, 2004 9 commits
  3. 10 Sep, 2004 4 commits
  4. 09 Sep, 2004 2 commits
  5. 04 Sep, 2004 3 commits
  6. 31 Aug, 2004 5 commits
  7. 27 Aug, 2004 2 commits
  8. 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
  9. 25 Aug, 2004 3 commits
  10. 23 Aug, 2004 2 commits