SilverTable.
The silver table of one source object: the shared header, the source object's declared fields as typed columns, and the layout rule its key chooses
Figure 1SilverTablespecified
- kind
- definition
- scope
- platform
- key
- the source object and its version
- store
- postgres
- family
- registers
Fields#
| field | type | required | note |
|---|---|---|---|
source_object | SourceObject | yes | |
name | text | yes | layer, source and object, one convention |
columns | Column | yes | the header’s columns and then the declared fields, typed, each with its version |
layout | one of by day | by entity bucket | yes | chosen by the key, never by hand |
key_field | [text] | yes | the ordered keys the layout follows; a table read from both ends declares both, and the writer keeps one copy under each |
version | count | yes | |
state | Readiness | yes | not ready when a declared field has no column |
Routes that use it#
No route takes or returns SilverTable directly. The record holds it, and the objects that point at it reach it.