On 4 Nov 2019, at 22:25, Jens Alfke wrote: >> 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.
For such fundamental and big changes, that’s exactly the problem. For the mainline SQLite we know that the code-base is regularly maintained and updated and that the official extensions work. Hence, I can base a product on it. For such a big new feature/method, which would be at the core of my product, I either have to maintain it myself (heavy) or hope that it’s not a dead-end… the risk profile is just not good. Viele Grüsse. -- Robert M. Münch
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
