[Zope-Checkins] CVS: Zope2 - CHANGES.txt:1.287.2.89
Jim Fulton
jim@digiciool.com
Thu, 15 Mar 2001 08:50:46 -0500 (EST)
Update of /cvs-repository/Zope2/doc
In directory korak:/tmp/cvs-serv29291
Modified Files:
Tag: zope-2_3-branch
CHANGES.txt
Log Message:
Added BTree/Cataloh changes.
--- Updated File CHANGES.txt in package Zope2 --
--- CHANGES.txt 2001/03/12 21:27:27 1.287.2.88
+++ CHANGES.txt 2001/03/15 13:50:45 1.287.2.89
@@ -105,6 +105,37 @@
security assertions, which meant that it could not be accessed
from DTML as advertised.
+ - Key errors were returned from catalog searches due to bugs
+ in unindexing objects.
+
+ - Objects that should have been included in search results
+ were excluded do to bugs in indexing objects.
+
+ - The database grew too fast when objects were routinely
+ indexed one at a time by the catalog. This was due to
+ inefficiencies in the underlying BTree implementation that
+ caused too many objects to be changed when indexing
+ incrementally. In addition, the set implementation, used for
+ keeping track of documents in field indexes, when the number
+ of documents per key was large, caused large database updates
+ when a document was added or removed, because the entire set
+ was stored in a single database record.
+
+ A new BTree and set implementation has been
+ provided to address these problems.
+
+ - The catalog is the most common source of conflict errors due
+ to a number of "hot spots" in the implementation and due to
+ the large number of objects that are typically updated when
+ indexing. The hot spots have now been removed and the
+ number of objects modified when indexing has been
+ dramatically reduced. In addition, conflicts detected during
+ transaction commit can not usually be resolved using new
+ conflict-resolution protocols and conflict-resolution
+ support added to the catalog. These changes will not avoid
+ all conflicts, but will reduce conflicts significantly in
+ many cases.
+
Zope 2.3.1 beta 1
Bugs Fixed