On Fri, Mar 23, 2012 at 14:09, Ashod Nakashian <ashodnakash...@yahoo.com> wrote: >... > The overhead in size isn't an issue (at least not a major one) rather the > overhead of *speed* is. At least that's my argument. I need to expand that > section with both approaches with pros/cons, but first let's agree on the > topic debated: to custom format, or to not.
wc.db is always opened. In fact, it *must* be to look up any pristine information. Opening that database is the slowest operation. From that point, things are very fast. For simplicity's sake, I would recommend an initial solution using wc.db for the metadata. You could then write a test to see whether a custom format would significantly outperform sqlite, and discussion a change at that point. IOW, do not "prematurely optimize". Go with the straightforward sqlite-based solution and test/validate the speed in a future review. Cheers, -g