[Zodb-checkins] CVS: ZODB3 - NEWS.txt:1.17.2.20

[Barry Warsaw]

Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv31679

Modified Files:
      Tag: ZODB3-3_1-branch
	NEWS.txt 
Log Message:
Updated for 3.1.1b2


=== ZODB3/NEWS.txt 1.17.2.19 => 1.17.2.20 ===
--- ZODB3/NEWS.txt:1.17.2.19	Tue Jan 28 12:52:36 2003
+++ ZODB3/NEWS.txt	Mon Feb  3 12:04:30 2003
@@ -1,6 +1,6 @@
 What's new in ZODB3 3.1.1 beta 2?
 =================================
-Release date: XX-XXX-2003
+Release date: 03-Feb-2003
 
 The Transaction "hosed" feature is disabled in this release.  If a
 transaction fails during the tpc_finish() it is not possible, in
@@ -9,10 +9,10 @@
 confirmation of the commit to the client.  If multiple storages are
 involved in a transaction, the problem is exacerbated: One storage may
 commit the data while another fails to commit.  In previous versions
-of ZODB, the database would set a global variable "hosed" that
-prevented any other transaction from committing until an administrator
-could check the status of the various failed storages and ensure that
-the database is in a consistent state.  This approach favors data
+of ZODB, the database would set a global "hosed" flag that prevented
+any other transaction from committing until an administrator could
+check the status of the various failed storages and ensure that the
+database is in a consistent state.  This approach favors data
 consistency over availability.  The new approach is to log a panic but
 continue.  In practice, availability seems to be more important than
 consistency.  The failure mode is exceedingly rare in either case.
@@ -31,10 +31,25 @@
 module BTrees.check for the checker and other utilities for working
 with BTrees.
 
+A new script called repozo.py was added.  This script, originally
+written by Anthony Baxter, provides an incremental backup scheme for
+FileStorage based storages.
+
+zeopack.py has been fixed to use a read-only connection.
+
+Various small autopack-related race conditions have been fixed in the
+Berkeley storage implementations.  There have been some table changes
+to the Berkeley storages so any storage you created in 3.1.1b1 may not
+work.  Part of these changes was to add a storage version number to
+the schema so these types of incompatible changes can be avoided in
+the future.
+
+Removed the chance of bogus warnings in the FileStorage iterator.
+
 ZEO
 ---
 
-The ZEO version number was bumped to 2.0.2 on account of the below
+The ZEO version number was bumped to 2.0.2 on account of the following
 minor feature additions.
 
 The performance of full cache verification has improved dramatically.
@@ -52,6 +67,8 @@
 If a client was disconnected during a transaction, the tpc_abort()
 call did not properly reset the internal state about the transaction.
 The bug caused the next transaction to fail in its tpc_finish().
+Also, any ClientDisconnected exceptions raised during tpc_abort() are
+ignored.
 
 What's new in ZODB3 3.1.1 beta 1?
 =================================