toofishes says: ------------------------------------------------------------------------ Here are the things to "do" since you don't seem to understand we are "busy" developing "software" that works and doesn't "break" people's systems in the "name" of speed. ------------------------------------------------------------------------
Why should the sqlite approach "break people's systems in the name of speed"? You clearly don't know what are you talking about... I really hope there are also competent pacman devs there (as you say).
I think this was discussed many times here, why we prefer the current backend: Simply because we are paranoid; we afraid of the following "message": "~Database is corrupted, restore it from backup", and we got a cryptic bunch of bytes as database. Saying not competent just because he doesn't agree with you is not a good argument. Well, probably we are not dbms experts, so instead of flaming you should convince us, why using your method is safe. I add one argument here: maybe using a professional dbms would reduce memory usage; but I am incompenent here, indeed ;-) Bye ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/