This document is archived and information here might be outdated. Recommended version. |
Esri Index object.
The Index object represents an index on a table. There are two types of indexes: spatial and attribute.
Spatial indexes exist on the shape field of a feature class. Some of the spatial index parameters, for example, the grid size, are only accessible through the GeometryDef object available from the shape field. The spatial index is created automatically when a geodatabase feature class is created, so you do not have to create the spatial index with ArcObjects. However, it is possible to delete and recreate the spatial index.
Attribute indexes are based on an ordered list of one or more fields in a table. The order of the list determines which field is used first when resolving data queries. There is a limit of ten fields in a geodatabase attribute index.
For geodatabases, there is one attribute index that is automatically created. This is the index on the Object ID. Another point to note is that you can access indexes created in the native environment of the DBMS.
For shapefiles, both spatial and attribute indexes can be manipulated, though note the usual limit of one field in an attribute index.
Index objects are not appropriate for use with INFO based data such as coverages. The equivalent functionality is available from the IArcInfoTable interface. See the section on coverage specific interfaces for more details.
Interfaces | Description |
---|---|
IClone (esriSystem) | Provides access to members that control cloning of objects. |
IGPDescribe | Provides access to a Geoprocessing description. |
IGPValue | Provides access to members of a GPValue. |
IIndex | Provides access to members that return information about the index. |
IIndexEdit | Provides access to members that modify the index. |
IPersist (esriSystem) | |
IPersistStream (esriSystem) | |
IXMLSerialize (esriSystem) | Provides access to members that XML serialize and deserialize an object to/from XML. |