Module rooted

Module rooted 

Source
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§

DataModelEntities
Which STEP instances the data model’s entities table carries.

Functions§

declares_global_id 🔒
Whether the schema registry lists type_name as declaring a GlobalId, i.e. as an IfcRoot subtype. A type the registry does not know answers false: for those the extracted global_id (read at the IfcRoot position by the metadata fallback) is the only evidence there is.
referenced_ids 🔒
Every entity id another table of data_model points at. 0 is the tables’ “none” (a root spatial node’s parent, a synthetic relationship’s rel_id), never an instance, so it is skipped.
retain_rooted_entities 🔒
Keep the entity rows a rooted-only client can need, dropping the rest.