see https://github.com/zopefoundation/ZODB/issues/16

when objects had been added in readCurrent

still need to come up with a test

string representation.

https://bugs.launchpad.net/zodb/+bug/993350

  Conflict resolution failed when state included cross-database
  persistent references with classes that couldn't be imported.

the fix fix.

  Conflict resolution failed when state included persistent references
  with classes that couldn't be imported.

"Blob temp file get's removed before it should",
https://bugs.launchpad.net/zodb/+bug/595378

A way this to happen is that a transaction is aborted after the
commit process has started. I don't know how this would happen in
the wild.

In 3.10.3, the ZEO tpc_abort call to the server is changed to be
synchronous, which should address this case. Maybe there's another
case.

----------

- "activity monitor not updated for subconnections when connection
  returned to pool"

https://bugs.launchpad.net/zodb/+bug/737198

difference.

Simplified and optimized marshalling code.

MRUish.

In some experiments, this led to significant reductions in cache miss
rates.

Fixed typo in comment

https://bugs.launchpad.net/zodb/+bug/677751

----------

- ZEO server transaction timeouts weren't logged as critical.

https://bugs.launchpad.net/zodb/+bug/670986

while running tests.

----------

- 3.10 introduced an optimization to try to address BTree conflict
  errors arrising for basing BTree keys on object ids. The
  optimization caused object ids allocated in aborted transactions to
  be reused. Unfortunately, this optimzation led to some rather
  severe failures in some applications.  The symptom is a conflict
  error in which one of the serials mentioned is zero.  This
  optimization has been removed.

  inherited from object, which compares based on in-process address.)
  Now BTrees warn if an attempt is made to save a key with
  comparison inherited from object. (This doesn't apply to old-style
  class instances.) This will become an error in ZODB 3.11.