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

[Jeremy Hylton]

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

Modified Files:
	NEWS.txt 
Log Message:
Merge 3.1 release branch changes to trunk.


=== ZODB3/NEWS.txt 1.22 => 1.23 ===
--- ZODB3/NEWS.txt:1.22	Wed Oct 30 13:57:13 2002
+++ ZODB3/NEWS.txt	Mon Nov 18 17:49:17 2002
@@ -1,3 +1,51 @@
+What's new in ZODB3 3.2?
+========================
+Release date: ?
+
+The Sync extension was removed from ExtensionClass, because it was not
+used by ZODB.
+
+What's new in ZODB3 3.1.1?
+=========================
+Release date: XX-Nov-2002
+
+It was possible for earlier versions of ZODB to deadlock when using
+multiple storages.  If multiple transactions committed concurrently
+and both transactions involved two or more shared storages, deadlock
+was possible.  This problem has been fixed by introducing a sortKey()
+method to the transaction and storage APIs that is used to define an
+ordering on transaction participants.  This solution will prevent
+deadlocks provided that all transaction participants that use locks
+define a valid sortKey() method.  A warning is raised if a participant
+does not define sortKey().  For backwards compatibility, BaseStorage
+provides a sortKey() that uses __name__.
+
+Added code to ThreadedAsync/LoopCallback.py to work around a bug in
+asyncore.py: a handled signal can cause unwanted reads to happen.
+
+A bug in FileStorage related to object uncreation was fixed.  If an
+a transaction that created an object was undone, FileStorage could
+write a bogus data record header that could lead to strange errors if
+the object was loaded.  An attempt to load an uncreated object now
+raises KeyError, as expected.
+
+The restore() implementation in FileStorage wrote incorrect
+backpointers for a few corner cases involving versions and undo.
+These specific bugs have been fixed and new test cases were added to
+cover them.
+
+A bug was fixed in conflict resolution that raised a NameError when a
+class involved in a conflict could not be loaded.  The bug did not
+affect correctness, but prevent ZODB from caching the fact that the
+class was unloadable.
+
+The script Tools/zeopack.py was fixed to work with ZEO 2.  It was
+untested and had two silly bugs.
+
+Some C extensions included standard header files before including
+Python.h, which is not allowed.  They now include Python.h first,
+which eliminates compiler warnings in certain configurations.
+
 What's new in ZODB3 3.1 final?
 ===============================
 Release date: 28-Oct-2002