Could dbm requirement be removed?

Hi,

The only thing that the DBM is still being used for is the database of
checked-out versions for --use-internal-co.  Since the installation of
an appropriate DBM module often causes user problems (especially on
Solaris and Mac OS X), I was wondering if anybody has an idea how we
could remove this requirement (perhaps making it optional).

I don't think that this DB is used very intensively; maximum one read
and one write per file revision (though the individual entries are the
size of the files' contents).  The main advantage of using a capable DBM
here is that it reclaims the space when a file's fulltext is no longer
needed.

On the other hand, I just made an experiment and our test suite runs
without errors even using dumbdbm (modulo some ArtifactManager
problems).  dumbdbm is very inefficient; e.g.,

* keeps its index in memory
* rewrites the whole index to disk after every __del__()
* does not reclaim unused space

so it would only be an option for small repositories.  But maybe this,
or something comparably naive, could be offered for people who have
small repositories and don't want to bother with installing other things.

Ossi, maybe your FilesystemDB should be revived?

Michael

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1667&dsMessageId=2384190

To unsubscribe from this discussion, e-mail: [[email protected]].