If you applying NOT NULL constraint, why not extract it from json altogether as a separate column? What's the use of it in json?

You may construct it back on retrieval, if you need it in results.

In my personal project (a game) I use an indexed key + a JSONB to store the save state, which comes from Lua.

So I can have cassette.propxyz = {1, 2, “abc”, true}

And

local anotherprop = cassette.leprop

I remember this getting to the top of HN for at least two more times.

Is this new or something? Works amazing as a document backend.

A long time ago, I wrote an ORM to serialize/deserialize object data seamlessly into SQLite, with massive arrays of floats being stored as blobs.

In code, I could effectively mark which class members need to be stored/restored, and optionally provide a custom serialization function for them if needed.

The latter was effectively never necessary, because all the bases types and multi-dimensional arrays were handled by templates.

Really wish I open-sourced that thing then, but the corporate bureaucracy around that was tricky.

I remember sufficiently little about implementation details now that I think I can get to writing it again, without producing a copypasta of that code - and maybe I should :)

> (Aside: The hard bit may be getting a new enough SQLite, at the time of writing Homebrew on macOS has it, else you likely need to use an unstable source like nixpkgs-unstable.)

Or just download the source and build it! (Gasp!)

[flagged]

[dead]