I almost pulled out all my hair trying to figure this one out. After applying limits using
the search kept returning only false. getLastError() and getLastWarning() contained empty strings.
The solution, like Nayana stated, is to add a positive non-zero integer $max to setLimit.
(PECL sphinx >= 0.1.0)
SphinxClient::setLimits — Set offset and limit of the result set
$max_matches= 0 [, int
$cutoff= 0 ]] )
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 stop searching at (
Result set offset.
Amount of matches to return.
Controls how much matches searchd will keep in RAM while searching.
Used for advanced performance control. It tells searchd to forcibly stop search query once
cutoffmatches have been found and processed.
TRUE on success or
FALSE on failure.
the max_matches / cutoff parameters are priceless.
if you ever have a situation where you need a 'count' of the number of matches, but only need to display lets say the 'top 10', these 2 parameters are very handy.
we used to get the occasional 'unable to connect' error with sphinx, after implementing these 2 parameters where applicable, these issues disappeared, load dropped, and the servers were much happier.
If you get an error
per-query max_matches=0 out of bounds (per-server max_matches=1000).
make sure that you also set the $max to a value other than the default 0,
there is an issue published with a patch if you feel like wanting to patch,
the first option works well as a workaround.