3 ms·
For some of these pragmas you have the same issue with or without "editions", right? Busy timeout is per-connection. And then: if you're running in WAL mode, yo
by tptacek 4mo ago
For some of these pragmas you have the same issue with or without "editions", right? Busy timeout is per-connection. And then: if you're running in WAL mode, you, the user, have to know that, or risk messing up the database by copying just the .db file rather than vacuuming-into.
- kccqzy 4mo agoEditions make the problem worse by requiring the version not only to support the underlying pragmas but also to understand the edition mapping. Example: PRAGMA foo=1 is introduced in 2027. PRAGMA edition=2030 implies this foo pragma. Now you unnecessarily lock out three years worth of releases.
- tptacek 4mo agoI don't see how you don't have the pragma compatibility problem either way. The edition proposal captures a bunch of behaviors that already exist.
- kccqzy 4mo agoYes, the problem exists either way. Editions just exacerbate the problem.
- PunchyHamster 4mo agofeature-set would be a better idea, because it is more explicit on what you are enabling
- amluto 4mo agoThere’s no need to store the literal edition in the DB file. Instead the edition could be a library construct that sets appropriate flags. So if you set edition 2026 you get WAL, etc.