thought this support already existed, but found out I was wrong when I
tried to make it work. :/) Applications for this include compression
and encryption.  An example wrapper storage implementation,
ZODB.tests.hexstorage, was included for testing.

It is important that storage implementations not assume that
storages contain pickles.  Renamed IStorageDB to IStorageWrapper and
expanded it to provide methods for transforming and untransforming
data records.  Storages implementations should use these methods to
get pickle data from stored records.

can fail if the pickle has been transformed and a calling storage
doesn't account for that.  Printing is certainly not the right way to
deal with the problem.

Also cleaned up some whitespace.

iterator implementations should just raise StopIteration, which
means they can now be implemented as generators.

  The filestorage packer configuration option noe accepts calues of
  the form ``modname:expression``, allowing the use of packer
  factories with options.

  The file-storage backup script, repoze, will now create a backup
  index file if an output file name is given via the --output/-o
  option.

(Merged the tseaver-repozo_index branch.)

sucking up a lot of time, as shown in some profile output.

This is to tr to warn people of likely design mistakes.  There is a
new option (large_record_size/large-record-size) to control the
Index: src/CHANGES.txt

methods for transforming and untransforming data records. This was
needed to make storage wrappers that transform data work with
conflict resolution.

- Can use it as a decorator

- Can omit the label, and get the label from the assertion function.

- You can now pass storage keyword arguments to ZODB.DB and
  ZODB.connection.

- You can now pass None (rather than a storage or file name) to get
  a database with a mapping storage.

(transaction-manager attempts method) introduced in the
``transaction`` 1.1.0 release.

made moot by the introduction of multi-version concurrency control
several years ago.

  BTree sets and tree sets didn't correctly check values passed to
  update or to constructors, causing Python to exit under certain
  circumstances.

and close_changes_on_close, to control whether underlying storages
are closed when the DemoStorage is closed.

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

  client-label configuration-file option to specify a label for a
  client in server logs. This makes it easier to identify specific
  clients corresponding to server log entries, especially when there
  are multiple clients originating from the same machine.

- to use with
- to use call_from_thread
- to try to recover from errors (that should never happen:)

Added timeout thread liveness to server status

- Improved ZEO server commit lock logging.  Now, locking activity is
  logged at the debug level until the number of wating lock requests
  gets above 3.  Log at the critical level when the number of waiting
  lock requests gets above 9.

- ZEO servers no longer log their pids in every log message. It's just
  not interesting. :)