This document is archived and information here might be outdated. Recommended version. |
The search order used by the filter.
[Visual Basic .NET] Public Property SearchOrder As esriSearchOrder
[C#] public esriSearchOrder SearchOrder {get; set;}
[C++]
HRESULT get_SearchOrder(
esriSearchOrder* order
);
[C++]
HRESULT put_SearchOrder(
esriSearchOrder order
);
[C++] Parameters order [out, retval]
order is a parameter of type esriSearchOrder* order [in]
order is a parameter of type esriSearchOrder
SearchOrder gets the order in which spatial searches are applied by the RDBMS (ArcSDE). The spatial component of the search should generally be applied before the attribute component. The more spatially restrictive of the two should be used. In the following query, "Find all wells with particulate counts between 1000 and 1200 in within 5 miles of a school", the esriSearchOrderAttribute enumerator is more effective. If the filter geometry is the outline of the city of Modesto, California and the attribute query is "street_name = 'Main St.'" then esriSearchOrderSpatial should be used, as there are a large number of "Main St." records at a national level.
Please note that esriSearchOrderSpatial is the default option. The following esriSearchOrder enumeration values are used to set the search order:
esriSearchOrderAttribute
Sets the search order to attribute first.
esriSearchOrderSpatial
Sets the search order to spatial first.