to closs connection.  This showed up on windows but not linux or mac
os x. I wonder why.

cache and cleaning the cache.

shouldn't work reliably.  There's no text saying what it was for so
...

windows failures!

  Saving indexes for large file storages failed (with the error:
  RuntimeError: maximum recursion depth exceeded).  This can cause a
  FileStorage to fail to start because it gets an error trying to save
  its index.

counted properly.

avoid spurious test failures.

for a timeout.

Cleaned up code formatting.

cannot resolve.

(zodbguide) and published at http://docs.zope.org/zodb.

Fixed intermittent failures by making MVCCMappingStorage hold a per-connection snapshot of the database.

This changed the schema, so we have to use the schema
differently. Presumably the schema is private.

Added an option to disallow cross-database references.

debugging easier.

Include extra data in InvalidObjectReference exceptions to make
debugging easier.

Added an option to disallow cross-database references.

did not necessarily increase for every transaction.  Fixed and tested.

object can now *also* be used as an object with attributes mapped to
the root-object keys.

support.

  Python (2.5 and later) with statement::

db = ZODB.DB(...)
     with db.transaction() as conn:
          # ... do stuff with conn

This uses a private transaction manager for the connection.
  If control exists the block without an error, the transaction is
  committed, otherwise, it is aborted.

- Connections now have a public ``opened`` attribute that is true when
  the connection is open, and false otherwise.  When true, it is the
  seconds since the epoch (time.time()) when the connection was
  opened. This is a renaming of the previous ``_opened`` private
  variable.