[Zodb-checkins] CVS: ZODB3/bsddb3Storage - NEWS:1.4

[Barry Warsaw]

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

Modified Files:
	NEWS 
Log Message:
Updated NEWS.  I'm calling the next version 2.0 because the table
formats have changed.


=== ZODB3/bsddb3Storage/NEWS 1.3 => 1.4 ===
--- ZODB3/bsddb3Storage/NEWS:1.3	Fri Nov  2 17:02:34 2001
+++ ZODB3/bsddb3Storage/NEWS	Sat Nov  9 00:32:21 2002
@@ -1,4 +1,34 @@
-Changes to Berkeley Storage for ZODB/Zope
+Changes to the Berkeley storages for ZODB3
+==========================================
+
+2.0 beta 1 (08-Nov-2002)
+
+    All new implementations of Full and Minimal storages.  Highlights
+    include:
+
+      * No Berkeley lock exhaustion.  Because we use application locks
+        instead of BerkeleyDB locks, there's no need to allocate huge
+        lock files, and no possibility that large transactions will
+        run out of locks.
+
+      * No temporary commit logs.  Both storages now use an optimistic
+        write strategy to avoid the need for temporary log files.
+        This gives better disk and cpu performance.
+
+      * Autopacking (Full only).  Automatic packing of the Full
+        storage is implemented in a separate thread.  Autopacking is
+        like "classic" pack except that it doesn't normally do garbage
+        collection.  Since it only gets rid of old object revisions,
+        it should be faster than a classic pack.  You can specify
+        packing policies, such as how often to autopack, how far back
+        in the past to pack to, and how often you want the autopack
+        thread to perform a full gc classic pack.
+
+     Note that there was no official 1.0 final release, although the
+     closest thing to a 1.0 final was included in the ZODB 3.1
+     release.  However the table schemas are not compatible so if you
+     have to upgrade an existing storage to one of the new storages,
+     you will need to do a copyTransactionsFrom().
 
 1.0 beta 5 (02-Nov-2001)