sqlite.org/releaselog/3_3
> STRICT tables provide a prescriptive style of data type management, for developers who prefer that kind of thing.
github.com/GrapheneOS/Att
Finally. It was possible to use CHECK constraints for data storage type checks but it was verbose and a bit slow.
Conversation
SQLite's feature set and performance have gotten so much better in the past few years.
WAL2 and BEGIN CONCURRENT will zap almost any reason I'd consider something else:
* sqlite.org/cgi/src/doc/wa
* sqlite.org/src/doc/begin-
Already so much faster than db servers in most cases...
Replying to
There are currently edge cases for highly concurrent database usage where the WAL file can grow indefinitely if you rely on the concurrent automatic checkpoints not blocking other usage. WAL2 fixes it and will hopefully be merged and released as stable in the next year or so.
4
Replying to
WAL2 and BEGIN CONCURRENT are planned features under development rather than something already available. I mean that those future improvements will make it work a lot better in cases where you want to have concurrent writers rather than just 1 writer and N readers together.
1
1
Show replies
Replying to
They're documentation for upcoming features so it will likely improve a lot before they're released.
2