This document is archived and information here might be outdated.  Recommended version.


IPlugInDatasetHelper2 Interface (ArcObjects .NET 10.6 SDK)
ArcObjects Help for .NET developers > ArcObjects namespaces > Geodatabase > ESRI.ArcGIS.GeoDatabase > Interfaces > IP > IPlugInDatasetHelper2 Interface (ArcObjects .NET 10.6 SDK)
ArcObjects Library Reference (GeoDatabase)  

IPlugInDatasetHelper2 Interface

Provides access to members that help Plug-In datasets.

Product Availability

Available with ArcGIS Engine, ArcGIS Desktop, and ArcGIS Server.

Description

This interface allows a dataset helper to implement data source-level filtering of rows using a where clause.

Members

Name Description
Read-only property Bounds The extent of the dataset.
Read-only property ClassCount The number of classes in the dataset.
Read-only property ClassIndex The index of the named class.
Read-only property ClassName The name of the indicated class.
Method FetchAll Gets all the records in the database.
Method FetchByEnvelope Gets the records within the envelope (or the full extent if the envelope is null).
Method FetchByID Gets a record by object id.
Method FetchWithFilter Gets the records according to the envelope, where clause or FIDSet.
Read-only property Fields The field set of the indicated class.
Read-only property OIDFieldIndex The index of the oid field in the field set of the indicated dataset.
Read-only property ShapeFieldIndex The index of the shape field in the field set of the indicated dataset.

Inherited Interfaces

Interfaces Description
IPlugInDatasetHelper Provides access to members that help Plug-In datasets.

CoClasses that implement IPlugInDatasetHelper2

CoClasses and Classes Description

Remarks

This interface can be implemented to optimize queries if there is a way to filter results from the data source more efficiently than checking the attributes of each row one-by-one. For example, data sources that have indexes should implement this interface to take advantage of indexing.
Dataset helpers for data sources without an optimized method of querying (like indexing) do not need to implement this interface.