Remove needless "cleanup" code -- Transaction does not have
a __del__ method (but probably did at some earlier time).

1. Construction of Connections is an implementation detail.
   ZODB client code should never construct connections directly.

2. __init__ is not a method of IConnection.  It might be a method of
   some sort of connection factory api, if we had one.

connections.   Connections now get their database and related data
when they are constructed.  They no longer throw away this information
when they are closed.  (The old design that threw away the database
and related data did so to avoid memory leaks in Python 1.)

Fixed a multi-database connection-management bug. (The fix
necessitated the simplification.)

by virtue of being reachable from objects in databases, there is
a danger of ambiguity when an object is reachable from multiple
databases.  This ambiguity can lead to very subtle bugs with the
symtom that objects are in unexpected databases.

Introduced a check to refuse to commit when the ambiguity exists.

(This required changing the connection '_creating' attribute to a
dictionary.)

Secondary connections always need to be made from an existing
connection.

Added check to make sure we don't get references across incompatible
connections.

pass optional open arguments to secondary databases.

savepoint.

Forward port from 2.7 branch.

UndoSearch._readnext():  Add the transaction size to the return value.

the function was moved to serialize.py; this caused
a Zope3 test to fail.

Use a sane zdaemon tag.

- Added an "extended" reference format in preparation for adding
  cross-database references.

- Simplified referencesf and get_refs, added doc strings, and moved
  get_refs to be with the other serialization code.

Documented and slightly changed the api for get_refs.  Updated
  client code accordingly.

- Added an "extended" reference format in preparation for adding
  cross-database references.

- Simplified referencesf and get_refs, added doc strings, and moved
  get_refs to be with the other serialization code.

Documented and slightly changed the api for get_refs.  Updated
  client code accordingly.

be consistent with the code in serialize.py. (It currently isn't.)

database format. In particular, data records should always have two
pickles.

checkCrossDBInvalidations():  This is too clever.  Stick a
sync() call back in to make it clearer.

checkCrossDBInvalidations:  make this willing to wait longer in all,
and increase the sleep time per failing loop iteration.  The hope is
this will allow the test to pass on slower and/or "too busy" machines.
I can't test that, though, since I couldn't get the test to fail at
all on a Windows or a Linux box.

Point at correct zdaemon tag.

Revert rev 30607 -- Zope trunk actually does still use ZODB's _Persistence.c,
although ZODB doesn't.

Port from ZODB 3.2.

referencesf():  Use %r instead of %s format in the error message, else
the pickle shown is full of unprintable characters.

Remove unused code; Zope 2.8 already has its own copy.

Use a zdaemon tag.

Prepare to stitch in zdaemon from a tag.

Use the same Zope3 tag as Zope 2.8.

Connection (and IDataManager) grows a public .transaction_manager
attribute.

The related txn_mgr spelling of various method arguments is
now deprecated, and a "transaction_manager" spelling is added.

Change test.py to use zope.testing.testrunner, and update the
latter to Jim's development version.  Hardest part turned out
to be teaching ZODB's setup.py how to "build" this version of
zope.testing (it has a lot of packages in a test directory,
where the latter is not itself a package).

Incidentally repaired an oversight in building zope.interface
too.

Missed a socket address change.

Use ZConfig's new socket address types appropriately.

These config file keys changed:

section    key              was             is
-------    ---------------  --------------  -------------------------
zeo        address          socket-address  socket-binding-address
zeo        monitor-address  socket-address  socket-binding-address
zeoclient  server           socket-address  socket-connection-address

Stitch in ZConfig as an SVN external.
Use the same tag Zope trunk (2.8) is using.

This is probably hosed for a bit, since it's trying to delete and
re-insert ZConfig at the same time.

Collector 1788:  runzeo fails in 2.8

A patch from Mark Hammond to repair a new Windows-specific
gimmick in ZEOServer.setup_win32_signals().