|
From: | David Brown |
Subject: | Re: [Monotone-devel] Re: sqlite versus metakit |
Date: | Tue, 10 May 2005 16:54:09 -0700 |
User-agent: | Opera M2/8.0 (Linux, build 1095) |
Stanislav Karchebny <address@hidden> writes:Did you people consider metakit as backend storage?Only graydon can answer that.I highly doubt there's a need for such cruft as SQL queries parser for a librarian (vcs).
The code still needs to do queries. Writing SQL queries and having code parse them is a lot easier than using query primitives and building them up manually. With pre-compiled queries, you don't even have the "cruft" of a query parser.
I've no idea. My guess would be that it wouldn't be worth it, but I could well be wrong. The trendy thing to do would be to replace sqlite with git in some way, I suspect. That might also be worth considering.
I think the primary benefit of git is how it searches and manages the file tree, not really how it stores the result. Last I checked, git always stored full versions of each file, so that would make its repos grow a lot faster.
Dave
[Prev in Thread] | Current Thread | [Next in Thread] |