[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:  assigned
 Priority:  normal       |    Milestone:  1.1.0   
Component:  Matcher      |      Version:  SVN HEAD
 Severity:  normal       |   Resolution:          
 Keywords:               |    Blockedby:          
 Platform:  All          |     Blocking:          
-------------------------+--------------------------------------------------

Comment(by olly):

 Hmm, it seems to me that clone() is potentially a costly operation, so
 forcing a call to it for any use of a PostingSource subclass seems
 problematic, even without the wrapping problems.
 It's also a pain to force the user to define it - the earlier patch where
 you could leave it and get a default implementation which returns NULL so
 it doesn't work with multi-databases or
 remotely is easier to work with if you don't care about these situations.

 I also wonder if it's better to set the database in clone() and keep
 reset() as it is now - that seems more logical to me if we don't expect
 objects to have their database changed.

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