cmpilato@collab.net writes:
> To address this, Karl proposed the idea of storing the changed paths
> as a revision property. That is, as a person changes things in a txn,
> we will track the changed paths as a transaction property. Then, at
> commit time (where we already initialize the revision properties by
> copying the transaction's properties) those would become revision
> properties. Wah-lah, constant-time answers to "What changed in this
> revision?"
>
> It seems kinda Band-aid(tm)-ish to me, but only because of the
> redundancy aspect (we *can* derive that information, it just takes
> time proportional to the size of the changes made to any given
> revision). But if a Band-aid(tm) is what we need, then it's what we
> need.
Like Ben, I'm +1 on caching (I guess that was implied).
If there's another way, then great. But we can't seem to think of
one, and 5 minutes to print out the logs is unacceptable :-).
Besides, this cache never needs to be invalidated, so it's not as evil
as a cache *could* be.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 22:38:45 2002