We use sqlite, but my recommendation is unless there is a very specific
reason to use sqlite, don't.

In my case I need to use sqlite due to multiple glibc locking issues.
(db4 is really unhappy when built w/ one version of glibc and run on
another.. most likely due to various locking issues.)

Also I have a requirement to do basic database access over NFS.  While
this is generally unsafe, sqlite makes it "more" reliable as long as you
don't attempt concurrent access.  For my environment the benefits
outweigh the risks.

(sqlite is also considerbly slower then db4, due to the emulation
aspects..  it also takes more space.. etc..)

--Mark

Bernhard Rosenkraenzer wrote:
> Hi,
> we're just about to switch Ark Linux over to using rpm5 - so this would be the 
> right time for us to make other related changes.
> 
> The first thing coming to mind is the rpm database format -- we've been using 
> db4 so far, has anyone compared db4 and sqlite to see if switching to sqlite 
> has any benefits/drawbacks (speed, db file size, ...)?
> 
> Also, are there any known db backend specific bugs?
> 
> Thanks,
> bero
> ______________________________________________________________________
> RPM Package Manager                                    http://rpm5.org
> Developer Communication List                        rpm-devel@rpm5.org