On 2017-07-10 12:28, Jos Vos wrote:
On Mon, Jul 10, 2017 at 09:14:07AM +0100, Richard W.M. Jones wrote:
> The web page has:
> Improvements and stabilization of "ndb" (New RPM DB Format database
> The problem is that "NDB" is a custom homebrew database invented in
> the RPM codebase. I agree that because of licensing problems we need
> to move away from Berkeley DB, but why not switch to the obvious,
> bulletproof choice - Sqlite?
Totally agree with Rich. If the problem with sqlite is the lack of SQL
developers, I am highly motivated to work on all SQL queries needed for
such backend, leveraging the whole bunch of fantastic features in recent
SQLite is is totally different piece of cake (RDBMS vs. key/value).
If you say:
create table col1(key blob primary key, value blob) without rowid;/
you physically get no more/no less simple key/value store (given 30 more
lines of trivial code for implementing your favorite key/value lib
But you are right - sqlite is different piece of cake: sqlite has
powerful query language. Sqlite based backend gives the future advantage
that big chunk of the rpm code could be elegantly and declarative
offloaded to the query engine (with efficiency benefits as bonus).