Expand description
Which rows the data model’s entities table carries (issue #6034).
Its own module because it is a WIRE CONTRACT as much as a filter: the parse
routes read it off the query, the data-model cache key is built from it, the
fetch route selects by it, and the client sends it. One definition keeps
those four in step, the same shape as parquet_layout.rs.
Enums§
- Data
Model Entities - Which STEP instances the data model’s entities table carries.
Functions§
- declares_
global_ 🔒id - Whether the schema registry lists
type_nameas declaring a GlobalId, i.e. as anIfcRootsubtype. A type the registry does not know answersfalse: for those the extractedglobal_id(read at theIfcRootposition by the metadata fallback) is the only evidence there is. - referenced_
ids 🔒 - Every entity id another table of
data_modelpoints at.0is the tables’ “none” (a root spatial node’s parent, a synthetic relationship’srel_id), never an instance, so it is skipped. - retain_
rooted_ 🔒entities - Keep the entity rows a rooted-only client can need, dropping the rest.