SetSelect api command #15
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In addition to the SetSelect hack, I made SphinxQuerySet pickleable. May prove useful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi there, David
I did a quick job of adding in a SetSelect command. I'm sure you know about it, its very useful for using more advanced features of sphinx. It has been introduced in Sphinx 0.9.9 RC1
An example use-case is to find documents that have been published anywhere between a certain date range.
http://sphinxsearch.com/forum/view.html?id=3577
Once SetSelect has been set, filters can be applied to the search query.
http://www.sphinxsearch.com/docs/current.html#api-func-setselect