[Xapian-tickets] [Xapian] #429: Document should perhaps track changes directly

[Xapian]

#429: Document should perhaps track changes directly
---------------------------+------------------------------------------------
 Reporter:  olly           |       Owner:  olly     
     Type:  enhancement    |      Status:  new      
 Priority:  normal         |   Milestone:  1.2.x    
Component:  Backend-Brass  |     Version:  SVN trunk
 Severity:  normal         |   Blockedby:           
 Platform:  All            |    Blocking:           
---------------------------+------------------------------------------------
 Follow on from #250.

 I wonder if a Document object should track the changes made, rather than
 copy the old data and modify it.  Currently adding a new term to a
 document is unnecessarily O(number of terms indexing that document).  The
 current optimisation is still useful in the case of reindexing an
 unmodified (or slightly modified) document from the original source.

 Allowing iteration of the modified data is awkward - either we need
 specialised iterator subclasses to handle this, or we flatten the changes
 onto the old data to give the current representation when asked to
 iterate.

 Marking for 1.2.x as this probably doesn't require ABI or API changes.

-- 
Ticket URL: <http://trac.xapian.org/ticket/429>
Xapian <http://xapian.org/>
Xapian