Ferreteria/archive/v0.5/sql/node leaf

versions: 0.41, 0.42, 0.5

About

• Purpose: Values for nodes

Concept

Every leaf:

• has
  • a name (unique within the node)
  • a value
• is like a single field in a single record

History

• 2017-08-03 Started, because the need became apparent.
• 2020-01-16 redesigning for v0.4 (copied from Ferreteria/sql/tf leaf) - this became 0.41
• 2020-01-23 tweaking for v0.42
• 2021-01-19
  • "integer width is deprecated"; also decided it should be 8 bytes
  • Turns out LONGTEXT barfs at certain kinds of binary data, so changing to LONGBLOB.
• 2022-03-06 copying v0.42/sql/node_leaf verbatim for v0.5
  • "Type" is in the documentation but not the table design. I'm thinking that it should be defined by the code, which will determine the data format based on registered field names. When we want to implement searching, there can be a separate table for indexing individual field-types.

SQL

CREATE TABLE `node_leaf` (
  `ID`      BIGINT        NOT NULL AUTO_INCREMENT,
  `ID_Node` BIGINT        NOT NULL COMMENT "ID of node to which this value belongs",
  `Name`    VARCHAR(255)  NOT NULL COMMENT "field name of this value",
  `Value`   LONGBLOB  DEFAULT NULL COMMENT "value",
  PRIMARY KEY(`ID`),
  UNIQUE KEY(`ID_Node`,`Name`)
) ENGINE=InnoDB;