[Xapian-tickets] [Xapian] #182: Match decider should be set on enquire object, not as get_mset() param

[Xapian]

#182: Match decider should be set on enquire object, not as get_mset() param
-------------------------+--------------------------------------------------
 Reporter:  richard      |        Owner:  richard  
     Type:  defect       |       Status:  assigned 
 Priority:  normal       |    Milestone:  2.0.0    
Component:  Library API  |      Version:  SVN trunk
 Severity:  normal       |   Resolution:           
 Keywords:               |    Blockedby:  186      
 Platform:  All          |     Blocking:           
-------------------------+--------------------------------------------------
Changes (by olly):

  * milestone:  => 2.0.0


Old description:

> Currently, match deciders (and match spies) are specified by passing them
> as
> get_mset() parameters.  It would be neater, and reduce the excessive
> number of
> parameters passed to get_mset(), if there was a "set_match_decider"
> function,
> instead of these parameters.
>
> We could also use this style of API to support things like multiple match
> deciders, where each would be called in sequence, allowing only those
> documents
> which pass all deciders to be returned.  This would be useful if only a
> limited
> set of predefined match deciders were available (for example, in a remote
> search, or when calling from Python), and a combination of restrictions
> was desired.

New description:

 Currently, match deciders (and match spies) are specified by passing them
 as
 get_mset() parameters.  It would be neater, and reduce the excessive
 number of
 parameters passed to get_mset(), if there was a "set_match_decider"
 function,
 instead of these parameters.

 We could also use this style of API to support things like multiple match
 deciders, where each would be called in sequence, allowing only those
 documents
 which pass all deciders to be returned.  This would be useful if only a
 limited
 set of predefined match deciders were available (for example, in a remote
 search, or when calling from Python), and a combination of restrictions
 was desired.

--

Comment:

 Due to the blockage, this can't be done until 2.0.0.

-- 
Ticket URL: <http://trac.xapian.org/ticket/182#comment:4>
Xapian <http://xapian.org/>
Xapian