SQLite Forum

Kind request: Please make SHA3/? part of built-in functions
Login
>The reason that all the sometimes useful extensions are optional, rather than forced into every build, is because the 'Lite' part of SQLite is a real feature, taken seriously by the developers and appreciated by many clients who target smaller platforms.

True but IMO irrelevant if an optional feature is disabled by default (hence, OPTIONAL) and enabled only via some compile time define.  Those who don't want to 'bloat' their copy with unused to them features won't have to do anything different from before.

>When incorporated into a build instead of being a separate dynamically linked library, the extension code acts in nearly all respects just like built-in functions do.

Why then not incorporate this (SHA3) and all other 'official' extensions in the amalgamation code, disabled by default yet easily available to enable with a simple turn of a compile time define 'switch'?

As I'm one of those who would like a fully 'bloated' version of SQLite3 (all bells and whistles available) I would also like to propose the introduction of a single define 'switch' that enables all possible feature adding options at once.

(Perhaps, for those who like minimalist versions, a similar 'switch' to disable all but the absolutely necessary.)