(PECL sphinx >= 0.1.0) Set offset and limit of the result set public bool SphinxClient::setLimits ( int $offset, int $limit [, int $max_matches = 0 [, int $cutoff = 0 ]] ) Sets offset into server-side result set and amount of matches to return to client starting from that offset (limit). Can additionally control maximum server-side result set size for current query (max_matches) and the threshold amount of matches to st

(PECL sphinx >= 0.1.0) Set per-index weights public bool SphinxClient::setIndexWeights ( array $weights ) Sets per-index weights and enables weighted summing of match weights across different indexes. Parameters: weights An associative array mapping string index names to integer weights. Default is empty array, i.e. weighting summing is disabled. Re

(PECL sphinx >= 0.1.0) Set a range of accepted document IDs public bool SphinxClient::setIDRange ( int $min, int $max ) Sets an accepted range of document IDs. Default range is from 0 to 0, i.e. no limit. Only those records that have document ID between min and max (including IDs exactly equal to min or max) will be matched. Parameters: min Minimum ID value.

(PECL sphinx >= 0.1.0) Set attribute name for per-group distinct values count calculations public bool SphinxClient::setGroupDistinct ( string $attribute ) Sets attribute name for per-group distinct values count calculations. Only available for grouping queries. For each group, all values of attribute will be stored, then the amount of distinct values will be calculated and returned to the client. This feature is similar

(PECL sphinx >= 0.1.0) Set grouping attribute public bool SphinxClient::setGroupBy ( string $attribute, int $func [, string $groupsort = "@group desc" ] ) Sets grouping attribute, function, and group sorting mode, and enables grouping. Grouping feature is very similar to GROUP BY clause in SQL. Results produced by this function call are going to be the same as produced by the following pseudo code: SELECT ... GROUP BY

(PECL sphinx >= 0.1.0) Set anchor point for a geosphere distance calculations public bool SphinxClient::setGeoAnchor ( string $attrlat, string $attrlong, float $latitude, float $longitude ) Sets anchor point for a geosphere distance (geodistance) calculations and enables them. Once an anchor point is set, you can use magic "@geodist" attribute name in your filters and/or sorting expressions. Parameters:

(PECL sphinx >= 0.1.0) Add new integer range filter public bool SphinxClient::setFilterRange ( string $attribute, int $min, int $max [, bool $exclude = false ] ) Adds new integer range filter to the existing list of filters. Only those documents which have attribute value stored in the index between min and max (including values that are exactly equal to min or max) will be matched (or rejected, if exclude is TRUE).

(PECL sphinx >= 0.1.0) Add new float range filter public bool SphinxClient::setFilterFloatRange ( string $attribute, float $min, float $max [, bool $exclude = false ] ) Adds new float range filter to the existing list of filters. Only those documents which have attribute value stored in the index between min and max (including values that are exactly equal to min or max) will be matched (or rejected, if exclude is TRUE).

(PECL sphinx >= 0.1.0) Add new integer values set filter public bool SphinxClient::setFilter ( string $attribute, array $values [, bool $exclude = false ] ) Adds new integer values set filter to the existing list of filters. Parameters: attribute An attribute name. values Plain array of integer values. exclude

(PECL sphinx >= 0.1.0) Set field weights public bool SphinxClient::setFieldWeights ( array $weights ) Binds per-field weights by name. Match ranking can be affected by per-field weights. See » Sphinx documentation for an explanation on how phrase proximity ranking is affected. This call lets you specify non-default weights for full-text fields. The weights must be positive 32-bit integers, so be careful not to hit 32-