On Mon, Sep 15, 2014 at 7:37 PM, Cristian Rodríguez
El 15/09/14 a las #4, Jan Engelhardt escribió:
Perhaps someone should explore splitting data up into more tables, or adding indexes, or replacing the Berkeley DB backend by LMDB or SQLite.
I agree that the rpm database should be backed by something like sqlite..however I am not sure how well that idea will be received :-)
I wouldn't do that, unless you can accept frequent reconstruction of the db. RPM's database should be resilient, and while sqlite isn't as bad a plain text files, it's still not something people use as production, crash-resilient databases. MySQL databases, not only need mysql (good luck making it a dependency of rpm) but also are quite big by default when using innodb (which is the least you can do if you want crash safety). All in all, bdb isn't so bad. But a change in the access pattern for rpm -qa might be welcome. I'm sure some incarnations of bdb support sequential scan at least in some db configuraitons. Not sure what's applicable for rpm though. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org