37 lines
1.3 KiB
Plaintext
37 lines
1.3 KiB
Plaintext
|
From: skip at mojam.com (Skip Montanaro)
|
||
|
|
Date: Thu, 22 Apr 1999 03:08:35 GMT
|
||
|
|
Subject: Need someone to try some rarely used bsddb methods
|
||
|
|
References: <7fa14m$vfm$1@nnrp1.dejanews.com>
|
||
|
|
Message-ID: <371E9326.8472D97@mojam.com>
|
||
|
|
Content-Length: 1057
|
||
|
|
X-UID: 405
|
||
|
|
|
||
|
|
A few days ago I asked for input about how the various bsddb object
|
||
|
|
methods work with different storage types (btree, hash, recno). I got
|
||
|
|
responses from several people whose findings were consistent with mine.
|
||
|
|
The "last" and "previous" methods seemed to fail for hash databases.
|
||
|
|
|
||
|
|
It turns out they aren't supported. A little digging around in the
|
||
|
|
Berkeley DB code demonstrated that quite clearly. I will work on some
|
||
|
|
patches to the bsddb module that catch the mistake and return a more
|
||
|
|
meaningful error message along with the exception. I have yet to figure
|
||
|
|
out what is happening with the recno format databases. My
|
||
|
|
recommendation is that you only use the btree format for large
|
||
|
|
databases. (Unfortunately, anydbm.open calls bsddb.hashopen when it's
|
||
|
|
available.)
|
||
|
|
|
||
|
|
I wound up writing the section for the library reference as well. I
|
||
|
|
believe it's in the CVS repository now.
|
||
|
|
|
||
|
|
Thanks to all who replied.
|
||
|
|
|
||
|
|
--
|
||
|
|
Skip Montanaro | Mojam: "Uniting the World of Music"
|
||
|
|
http://www.mojam.com/
|
||
|
|
skip at mojam.com | Musi-Cal: http://www.musi-cal.com/
|
||
|
|
518-372-5583
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|