[elephant-ticket] #41: Break up transaction while iterating over a btree

[elephant]

#41: Break up transaction while iterating over a btree
-------------------------+--------------------------------------------------
 Reporter:  ieslick      |       Owner:  ieslick      
     Type:  defect       |      Status:  new          
 Priority:  minor        |   Milestone:  Release 0.9.2
Component:  system-wide  |     Version:               
 Keywords:               |  
-------------------------+--------------------------------------------------
 Understand how a read-dominated transaction effects locks.  Can we expose
 an API for iterating sections of the index in chunks if we don't need to
 have the whole operation be atomic?  This is especially important if
 we're, say, updating a bunch of objects but they don't need to be done at
 once.  We can update in batches of 100, release the read locks, commit and
 then do the next 100.  This is easier for classes because we know values
 are unique so pset(key+value) designates a unique starting point for the
 next transaction.

-- 
Ticket URL: <http://trac.common-lisp.net/elephant/ticket/41>
elephant <http://common-lisp.net/project/elephant>
elephant