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

[Tim Peters]

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

Modified Files:
      Tag: Zope-2_7-branch
	NEWS.txt 
Log Message:
DemoStorage:  Added implementations for registerDB() and new_oid().  As
Tres discovered the hard way, wrapping a ZEO client storage as a
DemoStorage base storage yields insane behavior otherwise.

BaseStorage.new_oid():  Rewrite to eliminate recursion, and hence also the
need for the undocumented and irregular `last=` argument.

Other:  removed the `last=` argument to new_oid() every place that felt
compelled to spread that insanity ;-).  Seriously, it served no purpose
at all elsewhere, and looks like people just cut 'n pasted in fear.


=== ZODB3/NEWS.txt 1.33.6.73 => 1.33.6.74 ===
--- ZODB3/NEWS.txt:1.33.6.73	Mon Apr 18 15:57:47 2005
+++ ZODB3/NEWS.txt	Fri Apr 22 15:36:07 2005
@@ -1,3 +1,29 @@
+What's new in ZODB3 3.2.7c3?
+============================
+Release date: 22-Apr-2005
+
+This was an internal release, to get ``DemoStorage`` repairs into the
+next Zope release.
+
+DemoStorage
+-----------
+
+Appropriate implementations of the storage API's ``registerDB()`` and
+``new_oid()`` methods were added, delegating to the base storage.  This was
+needed to support wrapping a ZEO client storage as a ``DemoStorage`` base
+storage, as some new Zope tests want to do.
+
+BaseStorage
+-----------
+
+``new_oid()``'s undocumented ``last=`` argument was removed.  It was used
+only for internal recursion, and injured code sanity elsewhere because not
+all storages included it in their ``new_oid()``'s signature.  Straightening
+this out required adding ``last=`` everywhere, or removing it everywhere.
+Since recursion isn't actually needed, and there was no other use for
+``last=``, removing it everywhere was the obvious choice.
+
+
 What's new in ZODB3 3.2.7c2?
 ============================
 Release date: 18-Apr-2005