Re:SQLite is all you need for durable workflows
by pseudalopex on Friday May 29, 2026 @08:49PM
(#48331229)
The price of compatibility could be a pragma.
Re:SQLite is all you need for durable workflows
by formerly_proven on Saturday May 30, 2026 @06:30AM
(#48334712)
It literally is? Changing the defaults shown in the PRAGMAs above would break backwards compatibility. SQLite is strictly semantically versioned and does not break backwards compatibility.
Re:SQLite is all you need for durable workflows
by pseudalopex on Saturday May 30, 2026 @12:34PM
(#48338054)
Their complaint was SQLite's type system was poor. You said this was the price of compatibility. And the documentation of your recommended pragmas said nothing of types. They seemed unrelated helpful advice seemingly.
New types would break forward compatibility in SQLite's terms. 3.7.0 added WAL mode was their example of a forward compatibility break.[1] 3.y.0 could add better type system mode.
Also use strict tables. https://www.sqlite.org/stricttables.html
While it has bad ergonomics, you can also use CHECK constraints. For example, using sqlite's built in date support, it's possible but awkward:
The IS NOT NULL is needed because date returns NULL for invalid dates; the other check because it also accepts Julian days (date('2026') is sometime during year 4707 BC).