Expand description
Every byte layout that crosses a ReifyDB boundary: the type-tag namespace, the self-describing value codec, the RBCF columnar frame format, the row storage codec, the key codec and the extern-C cells. Both halves live here and share one tag scheme, so no consumer hand-rolls these bytes.
Modules§
- constraint
- error
- extern_
c - frame
- json
- key
- Order-determining codec turning typed keys into the bytes that go on disk: a range scan reads
order straight off the bytes with no decode pass. Booleans, numbers and temporals are
bit-inverted and so sort descending; utf8, blobs and uuids are stored plain and sort ascending.
encode_*_ascare the uninverted integer forms for keyspaces that need a forward scan. - primitive
- Canonical byte layouts for every leaf value the database stores or transmits, one submodule per kind. A shipped layout is used by storage, replication, CDC and the wire protocol at once, so changing one is a coordinated cross-format break: old bytes must keep round-tripping.
- reader
- row
- The row envelope family types: the opaque
EncodedBytesa flat store hands back, the shape machinery that gives it a typed view, and one submodule per storage family that owns a header layout of its own. A family’s carve lands here as its own submodule. - tag
- typeinfo
- value