abstraction to make the code a little more readable while trying to
decipher the storage locking logic.

iteratng from a starting transaction near the end of the file, the
iterator will scan backward from the end of the file to find the
starting point.

satisfied.  Added waits to make the assumtions more explicit and to
try to make sure they were satisfied.

not run tests.

Removed test levels. Test levels are an invitation to inadvertently
not run tests.

merge a couple of years ago.  Fortunately, they still pass, so no new
release is indicated.

I didn't restore and removed one silly test class, OneTimeTests,
related to obsolete packing issues.

I didn't restore and removed another silly test class,
DemoStorageWrappedAroundClientStorage, because it is an error to wrap
a demo storage around a client storage. A DemoStorage should only wrap
a storage who's data never changes.

Removed test levels. Test levels are an invitation to inadvertently
not run tests.

anything. Returning a serial isn't practical with ZEO and it isn't
really needed anyway.

Added a missing interface declaration for IExternalGC to FileStorage.

staying under 5000 bytes.  There appears to be a race in the test.  If
the cleanup thread is slow enough, it will prevent later cleanup
threads from running. Need to think about this.

collection, http://wiki.zope.org/ZODB/ExternalGC, has been defined
and implemented for FileStorage.

initial data as a string argument to the Blob constructor.

blob-sie-check percent.

tpc_finish doesn't specify a return value and having one makes tests
messier.

file storages.

Also fixed a bug in handling the create option with blob support.

efficient packing (and undo).

ignored when doing GC.  That is, when traversing from the root, if a
reference object wasn't found, it was simply ignored, covering up a
potential problem.  Now raise a key error, which stops packing.

return an object count of 0.

that.

tests more precise to aid test debugging.

Changed the default blob-cache-size-check size to 10%.

Changed the algorithm for deciding the target for blob cache
reduction. Now the target is

blob-cache-size * (100 - blob-cache-size-check)/100

testing a storage. :)

Made it possible to opt out of recovery tests.