Julian Foad wrote:
> Daniel Shahaf wrote:
>
>>> Half of the lines of this function deal with storing new reps in the
>>> rep-cache DB. Some day it should also remove the old DB rows (and
>>> somehow cause references in other revisions into the revision-being-
>>> obliterated to still work).
>>>
>
> When you say "cache", is it a cache in the sense that functionally it
> doesn't matter whether it contains any or all of these things? From what
> you ssay below, it sounds like it is a "rep store". Please let me
> understand that clearly before I go on.
>
It's not a cache; that was an unfortunate choice of name. The filesystem
doesn't break if that database goes away, but afterwards representation
sharing doesn't ... well, share, at least not existing representations.
So you lose functionality in the sense that you can get duplicate
representations.
-- Brane
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2406624
Received on 2009-10-12 14:17:57 CEST