> On Nov 4, 2019, at 4:57 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > That's one of the reasons that the source code for SQLite is public: so that > people can add the features they want.
Totally agree. However, when you go off the mainline of SQLite you lose some things, like easy updating to new SQLite releases — you now have to deal with merging the new official SQLite into the forked SQLite, or waiting for the fork maintainer to do it. In the case of LiteTree, I suspect the merge would be pretty difficult because of the extensive changes — it must be replacing the whole B-tree layer to be using LMDB as storage. (There was an earlier project called SQLightning that did the same thing. I was tempted by it, but it was based on an old version like 3.9 and the author made it clear he had zero interest in updating.) I don't have a practical use for the branching features, though they're cool, but I'm salivating at the thought of a 2x speedup. With all the work that's put into eking out small performance increases in SQLite, I'd imagine the devs would be interested in something that made that big of a difference... —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
