Hi, I think both your requirements and Dr Hipp's point-of-view are valid if we continue to see SQLite as just a tool. Yes, SQLite is an amazing tool for all the things it does and especially for a great design which almost never stands in the way of user customization and extension. However, SQLite's user base has grown so much that it should not be seen just as a tool but also as a business with multiple use-cases to which it is applied.
The question of which features to enable by default to please everyone is not answerable if one continues to see it as a tool. However, if seen as a business, there may be a solution possible. The canonical way businesses approach this is to rely on its ecosystem - partners, resellers, app-stores etc. Such an approach is a win-win-win for core-tool-builder (by helping keep focus on key-features), customers (getting niche features without breaking a sweat) and partners. But this approach needs a willingness to nurture the ecosystem by providing , as needed, tech support, access to paying customer lists with niche requirements, funding, guidance etc - possibly in exchange for a cut and strong control over ecosystem tool's testing, metrics etc - in short, a Partner Program. I built one such SQLite ecosystem solution called StepSqlite - an advanced PL/SQL compiler which is backward compatible with subset of Oracle-TM PL/SQL. It is full of features which will blow your mind - one of the features, relevant here, is automatic detection and setting of SQLite pragmas and extensions based on user code. You simply write PL/SQL-like code for DB access and StepSqlite customizes a SQLite library baked with your code(translated to C++) and make it available to you as a shared library for download which can be used in your app(s) - which in turn can be written in any major client language and for any major OS without any bridge-layer (No JDBC-ODBC etc needed). I designed it specifically to target requirements like your's: > Without risk of bringing malware from other downloads. > Without the hassle of rebuilding it every time I need a new version. > Without having to remember one or two years later upon ... > Consistent across machines... > There are several such power features in StepSqlite (Pls. see this Google doc link for a list of StepSqlite features: https://docs.google.com/document/d/1037VTdEhuGYi8D6vVQ2KOD86fn9-qt4WVYVos9lpBqE/edit?usp=sharing) - I even added window-functions one year before SQLite core - and IMHO, is still a better value than core-version (because it works on older SQLite versions using just CTE , does not add complexity to core, has more included window-functions and is dead-easy to write custom ones. for ex, FUNCTION MyAvg(val float) RETURN float ANALYTIC is sum(val)/count(val); Needless to say, IMO, StepSqlite has a great value proposition but I am having a hard time funding it myself and reaching a critical mass of customers. If SQLite had a partner program I could bring it to market much faster and it would be a win-win-win instead of loose-loose-loose (SQLite core gets bulky loosing its key USP)-(users get upset because the required features take a lot of hand-customization)-(well-wishing potential partners like me languish). And I am just one such ecosystem solution of many: there are other great ones: for ex, bedrockdb, litereplica etc which would probably benefit from a well defined SQLite partner program. In any case, that would be my go-to solution for the issue at hand: SQLite partner program. Best Regards, S Kashikar On Tue, Dec 11, 2018 at 6:47 AM Digital Dog <[email protected]> wrote: > On Thu, Dec 6, 2018 at 8:06 PM Keith Medcalf <[email protected]> wrote: > > The issue is not limited to generate_series (although that one seems to be > pain point for many users). ... Projects using these platforms require > custom builds of sqlite > anyway. > > The ability to download and immediately start working with a really > capable shell. > Without risk of bringing malware from other downloads. > Without the hassle of rebuilding it every time I need a new version. > Without having to remember one or two years later upon returning to a > stuff that > need changes that there was a custom built sqlite shell there. > Consistent across machines, because it was just downloaded from official > download site. > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
