[Zope-Annce] ZODB 3.2.1b1 released

[Jeremy Hylton]

ZODB 3.2.1b1 was released from the regular location today:
    http://www.zope.org/Products/ZODB3.2

This is a bug fix release that tracks the Zope 2.7b3 release earlier
today.  The ZODB release was made from the same CVS tag as the Zope
release, so the shared code is nearly identical.  The final release of
ZODB 3.2.1 will match Zope 2.7 exactly.

I've included the latest news items below.

Jeremy

What's new in ZODB3 3.2.1 beta 1
================================
Release-date: 18-Nov-2003

This code in this release should be identical to the code in Zope
2.7.0 beta 3.

Changed the ZEO server and control process to work with a single
configuration file; this is now the default way to configure these
processes.  (It's still possible to use separate configuration files.)
The ZEO configuration file can now include a "runner" section used by
the control process and ignored by the ZEO server process itself.  If
present, the control process can use the same configuration file.

Fixed a performance problem in the logging code for the ZEO protocol.
The logging code could call repr() on arbitrarily long lists, even
though it only logged the first 60 bytes; worse, it calls repr() even
if logging is currently disabled.  Fixed to call repr() on individual
elements until the limit is reached.

ReadConflictErrors have an experimental new method, ignore().  If a
database connection raises a read conflict, the current transaction
was eventually be aborted.  If the ignore() method is called, it will
allow a transaction to commit after receiving a read conflict.  This
method should be used with great care, because ignoring read conflicts
may allow inconsistent data to be written to the database.

Several bare string exceptions were changed to raise exception
objects.  All these exceptions were in fairly obscure parts of the
code. 

Bug fix for Acquisition in ExtensionClass.  Zope Collector #1056:
aq_acquire() ignored the default argument.

The zdaemon.Daemon module was removed, because it is no longer used by
zdaemon.

The ZEO test suite is more robust.  A variety of small changes were
made that make it less likely to fail on slow or loaded machines.