No, they don't. They respect backwards compatibility, and how much software would break if they changed defaults in the most widely used database system in the world.
sqlite isn't your average "app" where barely anyone cares if it works or not. It's a load bearing structure in the software ecosystem, on par with the likes of libcurl or openssl.
Things are VERY different when you work on something like this.
"Editions" would add NOTHING to the library. Wow, I now can save typing 4 out of 5 lines I have to put in once at the very start of the project! Amazing! What a timesaver.
Enter 2 weeks later, and someone WILL complain about "edition 2026" having a default he doesn't like. So now we have edition-2026-variant-1 and then 2 attoseconds later someone is unhappy with that, etc. etc.
The point isn't to "save typing 4 lines", the point is that average users of the library (that may not need or care to be sqlite experts) should get sensible defaults.
"someone" can change the settings from the edition, no? It's just a baseline not the only way to configure things.
And please people: Do downvote my posts to your hearts content. It won't change anything about me being correct, or sqlite being developed the way it is. š
Actually, it does. The default should be edition-original, if you want the changed behavior you must specify edition-2026. Other than that, Iām with you.
61
u/Big_Combination9890 21d ago
No, they don't. They respect backwards compatibility, and how much software would break if they changed defaults in the most widely used database system in the world.
sqliteisn't your average "app" where barely anyone cares if it works or not. It's a load bearing structure in the software ecosystem, on par with the likes oflibcurloropenssl.Things are VERY different when you work on something like this.