Expand description
The row model both transports speak.
HTTP carries rows as YSON and RPC carries them in the wire protocol, and neither type belongs in an interface the other has to implement. This is the meeting point: a column name, and a value from the set both formats can represent.
Column names, not ids. The RPC wire format numbers its values and resolves them through a name table; HTTP names them directly. A caller should not have to know which, so the id is an implementation detail of the RPC side.
Structs§
- Row
- One row: named columns, in insertion order.
Enums§
- Value
- One column value.
Type Aliases§
- Maybe
Row - A row that may be absent.