SchemaManifest Class @beta
The reference graph of every schema in one iModel - names, versions and reference edges, without schema items. A SchemaViewDataProvider builds it from ECDbMeta rows via fromRows. It includes schemas excluded from SchemaView's binary data.
SchemaViewManager uses this graph to determine which schemas a filtered request needs. The manifest does not track which schemas are already loaded; the manager filters the result of getSchemaClosure itself.
Methods
| Name | Description | |
|---|---|---|
| constructor(entries: ReadonlyArray<SchemaManifestEntry>): SchemaManifest | Wraps a set of entries whose references are already wired to one another. | |
| findByName(name: string): SchemaManifestEntry | undefined | The entry for a schema by name (case-insensitive), or undefined if the iModel has no such schema. |
|
| getAvailableSchemaNames(): string[] | The names of every schema in the iModel, in manifest order. | |
| getSchemaClosure(requestedNames: Iterable<string>): string[] | The transitive reference closure of the requested schemas, as a flat, duplicate-free list of | |
| fromRows(schemaRows: ReadonlyArray<SchemaManifestSchemaRow>, referenceRows: ReadonlyArray<SchemaManifestReferenceRow>): SchemaManifest Static | Build a manifest from raw ECDbMeta query rows, so a SchemaViewDataProvider only has to run |
Properties
| Name | Type | Description | |
|---|---|---|---|
| entries Accessor ReadOnly | ReadonlyArray<SchemaManifestEntry> | ||
| schemaCount Accessor ReadOnly | number | The number of schemas in the iModel. |
Defined in
Last Updated: 30 September, 2026
Found something wrong, missing, or unclear on this page? Raise an issue in our repo.