Additional core changes to support querying the SystemDb

The following are recent core changes implemented to support querying the SystemDb.

Orient Indexes
There is support for Orient Indexes to improve performance of queries against the SystemDb, as well as improved performance in hierarchy navigation. For details, see “orientSystemDb-OrientIndex”, in the Components section.
The n:station implied tag in the NiagaraTagDictionary
The n:station tag is added to all indexed entities identifying the entity’s source station.
- Query the entire SystemDb for all devices from a particular subordinate station:
  sys:|neql:n:device and n:station = 'DeviceName'
  NOTE: The above example would be slow to process because it must scan the entire SystemDb. A scoped query (using an ORD base that is the root of the indexed device entities) is a more efficient way to perform the same query (e.g., ip:<SupervisorIP>|foxs:|nspace:DeviceName|slot:/|sys:|neql:n:device).
There is added support for NEQL over fox connections (supporting BQL queries piped onto the results of NEQL queries), which displays as a collection table in Workbench or the browser.
- Displays a collection table with a single ORD column:
  ip:<SupervisorIP>|foxs:|sys:|neql:n:device
- Displays a collection table with two columns (Status and NavOrd):
  ip:<SupervisorIP>|foxs:|sys:|neql:n:device|bql:select status, navOrd
There is added support for translated px graphics on virtual components loaded on demand.
- This is equivalent to having px graphics imported to the Supervisor station via export tags, but without the additional setup. For details, see “Viewing Virtual Px graphics on demand” in the section on “ Niagara virtuals cache (virtual Policies)” in the Niagara Drivers Guide.

Additional core changes to support querying the SystemDb

Related Links

Related Tasks

Related References