[Xapian-tickets] [Xapian] #295: Add support for multi and remote databases with PostingSources

[Xapian]

#295: Add support for multi and remote databases with PostingSources
-------------------------+--------------------------------------------------
 Reporter:  richard      |        Owner:  richard  
     Type:  enhancement  |       Status:  closed   
 Priority:  normal       |    Milestone:  1.1.0    
Component:  Matcher      |      Version:  SVN trunk
 Severity:  normal       |   Resolution:  fixed    
 Keywords:               |    Blockedby:           
 Platform:  All          |     Blocking:  206      
-------------------------+--------------------------------------------------
Changes (by olly):

  * status:  reopened => closed
  * resolution:  => fixed


Comment:

 I realise it's not a highly performance sensitive area.  I noticed that
 this was inconsistent with a similar existing API, and was flagging that
 this, and while thinking about it, it struck me that the use of namespaces
 rather pessimised the use of a map.  But I think namespacing the name does
 make most sense.

 Good point that any incompatible change in Xapian::Weight names for built-
 in classes is highly unlikely to actually break user code (user weighting
 schemes will need changing anyway, so it wouldn't be a huge deal if they
 did).

 But applying a patch to change the weight names now is just going to
 causes conflicts with my uncommitted Xapian::Weight::Internal rewrite, and
 it's going to be easier to less work to just change the names in that.  So
 thanks, but no thanks...

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