3 ms·
The important point to keep in mind is that SQLite will read JSON5, but it never writes it. The JSON that SQLite generates is canonical JSON that is fully comp
by SQLite 3y ago
The important point to keep in mind is that SQLite will read JSON5, but it never writes it. The JSON that SQLite generates is canonical JSON that is fully compliant with the original JSON spec.
It turns out that there is a lot of "JSON" data in the wild that is not pure and proper JSON, but instead includes some of the extensions of JSON5. The point of this enhancement is to enable SQLite to read and process most of that wild JSON.
This feature was requested by multiple important users of SQLite.
- alberth 3y agoDr. Hipp Off topic: would you mind sharing any info on potential timing of begin-concurrent-pnu-wal2 branch being merged into main (or consideration of forking sqlite to have a "client/server" version)? https://www.sqlite.org/src/timeline?r=begin-concurrent-pnu-wal2 https://www.sqlite.org/src/timeline?r=begin-concurrent-pnu-w... (Love what you have created. Thank you so much for all the years of amazing work)
- SQLite 3y agoThat branch has been renamed "bedrock" (after its principal user) and is up-to-date.
- sidewndr46 3y agoIsn't this just the YAML debacle all over again? Where virtually any sequence of text is "valid" (albeit meaningless) YAML?
- masklinn 3y agoWhile I don't care for JSON5 it's hardly "virtually any sequence of text", it rather hews closer to JavaScript content, rather than the very limited subset (ish) that is JSON.
- conradev 3y agoVirtually any sequence is not the same as adopting a specification five years after it’s been published and adopted by industry: https://spec.json5.org/ https://spec.json5.org/ I appreciate that SQLite can’t write the format, because those changes are human afordances