If we have a MutableKeyValue class that basically stores values in a mutable backing store, with mutation methods... then we should get exactly what we want.
On Tue, Mar 24, 2009 at 1:31 PM, Erik Holstad <[email protected]> wrote: > I agree that it is better to keep KeyValue as it is, creating a separate > Key > class for storing the deleteKeys. > > On Tue, Mar 24, 2009 at 1:07 PM, Erik Holstad <[email protected]> > wrote: > > > Yeah, that sounds ok. > > I'm not changing the values in the storefiles but just making keyValues > to > > store in > > the delete list etc, but I guess I don't really need to store KeyValues > can > > have some > > other format. Will think about it. > > > > >
