On Thu, Mar 9, 2017 at 3:05 PM, Keith Christian <keith1christ...@gmail.com> wrote:
> At some point it's time to use a different database engine or offload > to other code. Sqlite could easily burgeon to the size of the other > databases if everything asked for was included. Where, then, would we > get a small but still functional SQL engine? Ah, here we go again :) I knew this was coming. First, you can always #ifdef. Have you opened the amalgamation recently, and seen the large parts which can be enabled or disabled? Second, those basic math functions are no more (or less) important than the ones shipping with SQLite right now. By your argument, SQLite should ship with none. Third, you must have missed the evolution of SQLite these past few years which added large parts (FTS3|4|5, FKs, CTEs, RBU, Session, JSON1, Row Values, etc...) which are considerably larger than a few math functions. Last but not least, it's trivial to not use what's there and available and easily disabled at compiled time, or ignored at runtime. While using what's not there, and not readily available w/o developer skills, is considerably harder. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
