An error occurred fetching the project authors.
  1. 21 Mar, 2005 2 commits
  2. 11 Mar, 2005 1 commit
  3. 05 Nov, 2004 1 commit
  4. 28 Jun, 2004 1 commit
    • Tim Peters's avatar
      Mostly clarifications of the complicated state transactions · fc1ec799
      Tim Peters authored
      are in now (partly ZODB 3, partly ZODB 4, partly transitional).
      More is needed.
      Added new collaborations.txt, which spells out some dynamics
      of the system in a compact way.  This is in a format Jim used
      for Zope 3, essentially a flat-text and less-formal representation
      of UML sequence diagrams.
      fc1ec799
  5. 22 Jun, 2004 1 commit
    • Tim Peters's avatar
      Primary thrust here is to teach ZODB about zope.interface, · 349c8486
      Tim Peters authored
      and include that in the ZODB project.  While we're at it,
      include zope.testing too, as zope.interface depends on that,
      and we had copied zope.testing.loggingsupport.py into ZODB
      earlier anyway (and delete that unique copy here now).
      
      This also merges some changes made to the ZODB copy in
      Zope3 back into ZODB.
      349c8486
  6. 02 Jun, 2004 1 commit
  7. 14 May, 2004 1 commit
  8. 19 Apr, 2004 1 commit
  9. 24 Feb, 2004 1 commit
  10. 19 Feb, 2004 1 commit
    • Jeremy Hylton's avatar
      Merge zope3-zodb3-devel-branch to the Zope head (Zope 2 head). · d5327c25
      Jeremy Hylton authored
      Add support for persistent weak references.  The implementation is in
      pure Python right now; coptimizations.c was disabled.  We need to
      restore the C code before going to beta.
      
      The persistent reference format has evolved a little, but the code on
      the branch doesn't document it.  The ref is usually a an oid-class
      pair, where the class is an actual class object.  It can also be a
      list, for weak references, or a bare oid.
      
      Add support for data managers written against the ZODB4 transaction
      API.  The transaction implementation provides an adapter between the
      two interfaces.  There's a substantial doctest test suite for this
      feature.
      
      Add add() method to Connection to explicitly add an object and get it
      an assigned _p_oid.  It's possible to add an unconnected object; this
      isn't recommended, because it will be lost at pack time.
      d5327c25