Ties.DB protocol

The Ties.DB protocol should be compact yet extensible. That is why we have chosen EBML as the base message format.

Ties.DB protocol is used to manipulate data. Data definition is done onchain. See Creating tablespaces and tables.

Notes

• EBML is binary format. However for human readability we will use XML equivalent in this doc.
• Ties.DB EBML supports the following data types:
  • u: unsigned arbitrary precision integer
  • i: signed arbitrary precision integer.
  • f: IEEE-754 floating point number (32 or 64 bits).
  • s: printable ASCII text string.
  • 8: printable UTF-8 Unicode text string.
  • d: signed integer representing timestamp, in milliseconds after (or before) 2001-01-01T00:00UTC.
  • b: binary data, otherwise uninterpreted.
  • m: Master-Element - contains other EBML sub-elements of the next lower level.
• Please note that some types, for instance, d, differ from EBML reference. It represents date in milliseconds instead of nanoseconds. And u and i types can represent integers of arbitrary precision.

There are several types of messages:

• ModificationRequest - request to modify rows
• ModificationResponse - response to modification request
• RecollectionRequest - request to recollect (select) rows
• RecollectionResponse - response to recollection request
• Error - response in case of fatal error