Interface IInverseCache

Inverse relations are one of very important concepts in EXPRESS modeling which allows to mimic safe bi-directional relations between two objects. But because EXPRESS model is always flat list of entities some queries using inverse properties for navigation in model cause exponential cost if the data search. That is obviously not optimal. Inverse cache should help especially in cases where the IModel implementation doesn't have any secondary indexing mechanism for inverse relations. It can usually only be used outside of transaction. Starting transaction when caching is on might raise an exception. You should always keep inverse cache object inside of using statement.

Inherited Members

System.IDisposable.Dispose()

Namespace: Xbim.Common

Assembly: Xbim.Common.dll

Syntax

public interface IInverseCache : IDisposable

Properties

Size

Number of cached relations

Declaration

int Size { get; }

Property Value

Type	Description
System.Int32

Methods

Clear()

Removes all cached inverse relations.

Declaration

void Clear()