[Zodb-checkins] CVS: ZODB3 - NEWS.txt:18.104.22.168
tim.one at comcast.net
Thu Feb 24 17:41:55 EST 2005
Update of /cvs-repository/ZODB3
In directory cvs.zope.org:/tmp/cvs-serv2861
Give fsIndex an efficient maxKey() implementation.
This will (in a later checkin) be used to give FileStorage an "obviously
correct" way to determine the largest oid used in an .fs.index file.
=== ZODB3/NEWS.txt 22.214.171.124 => 126.96.36.199 ===
--- ZODB3/NEWS.txt:188.8.131.52 Thu Feb 24 14:59:03 2005
+++ ZODB3/NEWS.txt Thu Feb 24 17:41:25 2005
@@ -49,6 +49,15 @@
Collector #1676: ``zodb.pdf`` in the release tarball was damaged (truncated),
because CVS mistakenly believed it was a text file.
+An efficient ``maxKey()`` method was implemented for the ``fsIndex`` class.
+This makes it possible to determine the largest oid in a ``FileStorage``
+index efficiently, directly, and reliably, replacing a more delicate scheme
+that tried to keep track of this by saving an oid high water mark in the
+index file and incrementally updating it.
What's new in ZODB3 3.2.5?
More information about the Zodb-checkins