Sienna currently stores associations between components and supplemental attributes in an in-memory SQLite database. The schema is
CREATE TABLE supplemental_attributes(
attribute_uuid TEXT NOT NULL,
attribute_type TEXT NOT NULL,
component_uuid TEXT NOT NULL,
component_type TEXT NOT NULL
)
When a system is serialized to JSON, this SQLite table is converted to an array of arrays and written to the system JSON object. During system de-serialization, that arrays is converted back to a SQLite database.
The planned special handling for Sienna GridDB database IDs will need to handle these UUIDs. The important point is that UUIDs in the de-serialized table need to match the actual component/supplemental attribute UUIDs.
Sienna currently stores associations between components and supplemental attributes in an in-memory SQLite database. The schema is
When a system is serialized to JSON, this SQLite table is converted to an array of arrays and written to the system JSON object. During system de-serialization, that arrays is converted back to a SQLite database.
The planned special handling for Sienna GridDB database IDs will need to handle these UUIDs. The important point is that UUIDs in the de-serialized table need to match the actual component/supplemental attribute UUIDs.