Florian Weimer wrote:
On 11/24/2016 02:54 PM, Richard Hipp wrote:
On 11/24/16, Florian Weimer <fwei...@redhat.com> wrote:
I'd like to replace the use of Berkeley DB in RPM with SQLite.
The scenario is special in the follow way. There is no database server,
all access goes directly to the database. Unprivileged users without
write access to the RPM database are expected to run read-only queries
against the database. Privileged users (basically, root) is expected to
use locking to exclude concurrent writers. But read-only users should
not be able to stop acquisition of a write lock.
Is there a way to do this with SQLite?
Seems like quite a lot of burden to go this route. SQLite has a much larger
footprint than BDB, and much worse performance overall. As a compromise you
could use SQLightning, which replaces SQLite's Btree layer with LMDB. Since
LMDB *does* allow readers that don't block writers. But it would be more
efficient to just use LMDB directly, and not incur the overhead of the SQL
translation layer.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
