Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

PROPDESC_COLUMNINDEX_TYPE enumeration

Indicates whether or how a property can be indexed.

Syntax


typedef enum PROPDESC_COLUMNINDEX_TYPE { 
  PDCIT_NONE          = 0,
  PDCIT_ONDISK        = 1,
  PDCIT_INMEMORY      = 2,
  PDCIT_ONDEMAND      = 3,
  PDCIT_ONDISKALL     = 4,
  PDCIT_ONDISKVECTOR  = 5
} PROPDESC_COLUMNINDEX_TYPE;

Constants

PDCIT_NONE

Never generate any index on this property.

PDCIT_ONDISK

Always build the individual value index, but build the vector index only on demand.

PDCIT_INMEMORY

Obsolete.

PDCIT_ONDEMAND

Windows 7 and later. Build the individual value index or vector index the first time the index is used in a query to filter, group, or sort. After being generated the first time, the index is maintained for future queries. Most property indexes should be built on demand, because building and maintaining indexes is expensive and they should be built only if they will be used.

PDCIT_ONDISKALL

Windows 7 and later. Always build both the individual value index and the vector index.

PDCIT_ONDISKVECTOR

Windows 7 and later. Always build the vector index, but build the value index only on demand.

Remarks

Windows Search builds indexes for the values found in the property store to efficiently support filtering, sorting, and grouping over indexed properties. There are two kinds of indexes: an individual value index that indexes an item by single values, and a vector index that indexes all the vector values of a row as a single index entry.

Requirements

Minimum supported client

Windows Vista [desktop apps only]

Minimum supported server

Windows Server 2008 [desktop apps only]

Header

Propsys.h

IDL

Propsys.idl

 

 

Community Additions

Show:
© 2014 Microsoft