1. 29 Sep, 2004 2 commits
  2. 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
  3. 23 Sep, 2004 1 commit
  4. 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
  5. 14 Sep, 2004 4 commits
  6. 10 Sep, 2004 2 commits
  7. 09 Sep, 2004 1 commit
  8. 04 Sep, 2004 2 commits
  9. 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
  10. 27 Aug, 2004 1 commit
  11. 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
  12. 25 Aug, 2004 1 commit
  13. 20 Aug, 2004 1 commit
  14. 19 Aug, 2004 1 commit
    • Tim Peters's avatar
      Merge rev 27186 from trunk. · cccb242e
      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.
      cccb242e
  15. 18 Aug, 2004 1 commit
    • Tim Peters's avatar
      Forward port from Zope 2.7 branch. · c5d49a10
      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.
      c5d49a10
  16. 17 Aug, 2004 2 commits
  17. 13 Aug, 2004 1 commit
  18. 12 Aug, 2004 2 commits
    • Tim Peters's avatar
      Update release date. · 8c672807
      Tim Peters authored
      8c672807
    • Tim Peters's avatar
      Merge/port checkins to ZODB code made from Zope3. · 4d5f3a94
      Tim Peters authored
      This includes:
      
      r26945 | jim | 2004-08-06 18:30:44 -0400 (Fri, 06 Aug 2004) | 6 lines
         M /Zope3/trunk/src/persistent/tests/test_persistent.py
         M /Zope3/trunk/src/zope/event/tests.py
      
      Updated to work with the versions of doctest from Python with versions
        greater than or equal to 2.3.0 and less than 2.4.0.a2 and with
        versions greater than 2.4.0a2.
      
      r26482 | srichter | 2004-07-13 13:07:03 -0400 (Tue, 13 Jul 2004) | 2 lines
         M /Zope3/trunk/src/transaction/__init__.py
         M /Zope3/trunk/src/transaction/_transaction.py
         M /Zope3/trunk/src/transaction/tests/test_transaction.py
      
      Converted XXX to TODO.
      
      r25953 | sidnei | 2004-06-23 13:14:20 -0400 (Wed, 23 Jun 2004) | 1 line
         M /Zope3/trunk/src/ZODB/interfaces.py
         M /Zope3/trunk/src/transaction/_transaction.py
         M /Zope3/trunk/src/zope/app/rdb/__init__.py
         M /Zope3/trunk/src/zope/app/rdb/tests/test_zopedbtransactionmanager.py
      
      Add missing sortKey method to ZopeDBTransactionManager and DataManagerAdapter, and also add it to the interface.
      
      r25330 | alga | 2004-06-10 10:07:45 -0400 (Thu, 10 Jun 2004) | 4 lines
         M /Zope3/trunk/src/ZODB/Connection.py
         M /Zope3/trunk/src/ZODB/interfaces.py
         M /Zope3/trunk/src/ZODB/tests/testConnection.py
      
      Added an IConnection interface declaration on ZODB Connection.
      
      Jim says Tim Peters will be mad at him, but that's the right way to go.
      
      r25273 | philikon | 2004-06-06 04:43:57 -0400 (Sun, 06 Jun 2004) | 4 lines
      Changed paths:
         M /Zope3/trunk/src/BTrees
         M /Zope3/trunk/src/ZODB
         M /Zope3/trunk/src/persistent
      
      Ignore .so files.
      
      This fix should probably be merged to the original ZODB tree.
      4d5f3a94
  19. 11 Aug, 2004 4 commits
    • Tim Peters's avatar
      Mechanical changes in prep for 3.3c1 release. · 216d7ff9
      Tim Peters authored
      216d7ff9
    • Tim Peters's avatar
      dbab667e
    • Tim Peters's avatar
      0c1452d2
    • Tim Peters's avatar
      Merge rev 26990 from ZODB trunk. · e5ca81e7
      Tim Peters authored
      Improve thread-death error reporting in tests.
      
      Reworked the way some of the ZEO tests use threads, so that unittest is
      more likely to notice the real cause of a failure (which usually occurs in
      a thread), and less likely to latch on to spurious problems resulting from
      the real failure.
      
      Detail:  The TestThread class got the (unittest) test case as an argument,
      and remembered it.  If the run() method saw the thread die with an
      exception, it called testcase.fail() with the formatted exception.  But
      this can't work as apparently intended:  unittest's fail() raises an
      AssertionError then, and the piece of unittest running the test expects
      to catch that exception and append the message to the result object's
      list of failures.  But the piece of unittest running the test isn't on
      *this* thread's call stack!  It's on the main thread's call stack.
      So unittest simply raised an exception that wasn't noticed by anything,
      and the thread died then, leaving a traceback somewhere in the middle
      of the output.  unittest didn't know anything about that, and sometimes
      thought the test passed despite the thread failure.
      
      Alas, when a thread dies like this it's also got a decent chance of
      leaving things in a state where the test's final checking code can't
      succeed, but the checking code doesn't know the thread died either,
      and spurious unittest failures and errors could get reported then.
      
      Reworked things so that only the main thread ever tries to tell
      unittest that a test failed.  A TestThread remembers an exception-
      death now, but doesn't report it until the main thread tries to join
      it.  This way unittest knows the test failed; records and reports
      the true cause of failure; and, because tests generally join all their
      threads before doing their final checking, unittest stops the test
      before final checking if a thread death occurred, and so there's
      less chance of seeing reports of spurious errors and failures.
      e5ca81e7
  20. 27 Jul, 2004 2 commits
  21. 11 Jul, 2004 1 commit
  22. 10 Jul, 2004 1 commit
    • Tim Peters's avatar
      Forward port from Zope 2.7 branch. · 21e0b34e
      Tim Peters authored
      Repaired a bug wherein spurious error msgs could be produced after
      reporting a problem with an unloadable object (discovered by eyeball,
      while staring at the code to figure out what it actually does).
      
      Vastly expanded the module docstring, with a slimmed-down version of
      the new fsrefs docs on the ZODB Wiki.
      
      21e0b34e
  23. 08 Jul, 2004 1 commit
    • Tim Peters's avatar
      Zope3-dev Collector #139: Memory leak involving buckets and connections · ef6f9a6e
      Tim Peters authored
      Connection objects were typically immortal because the threaded
      transaction manager kept them in an ever-growing lists.  Reworked the
      transaction manager internals to use a simple implementation of weak sets
      instead.  This plugs all leaks in the test program attached to the
      collector report (which was leaking about 100KB/sec on my box).
      ef6f9a6e
  24. 02 Jul, 2004 1 commit
    • Tim Peters's avatar
      Collector #1397: testTimeStamp fails on FreeBSD · 9ff85cee
      Tim Peters authored
      Forward-porting from Zope 2.7.
      
      The checkFullTimeStamp() test was sensitive to unique mktime() behavior
      on FreeBSD.  See:
      
      http://lists.freebsd.org/pipermail/freebsd-standards/2003-November/000268.html 
      
      The purpose of this test is to exercise ZODB's TimeStamp object, so got
      rid of dependence on platform mktime() and time.timezone quirks --
      TimeStamp works in GMT, so how mktime() treats tm_isdst should be
      irrelevant in all TimeStamp tests.
      
      Also added a comment about the highly non-obvious numeric characteristics
      of TimeStamp's treatment of seconds (round-tripping is surprisingly
      inaccurate, but for a real reason).
      9ff85cee
  25. 22 Jun, 2004 1 commit