> > As far as signaling to the user if a key was updated or removed, I'm a bit > more partial to the idea of storing the operation in the value of the seq > tree. That we we could avoid doing a btree lookup in the log tree for every > row in the seq tree fold at query time. > > The log is mainly here to remove keys from the old index, and secondly tell to the app that the key have been removed for this sequence.
If there is a cheapest way to do it, then let's go. At that time the log was the easiest way to do it. Maybe the main index log could be merged with the seq log but not sure about that. It would make it a little more complex to handle at least. - benoit.
