Re: Minimizing the `revisions' table.

On Fri, Jun 14, 2002 at 03:21:23PM -0500, cmpilato@collab.net wrote:
> Greg Stein <gstein@lyra.org> writes:
...
> > Heck. I'm not even sure how you're going to populate this table. If
> > svn_fs_make_file() is called, then you're going to get an add. Some time
> > later, somebody is going to change its contents, so you'll get a "modify"
> > for its text, then another "modify" for its properties.
>
> Yeah, I just independently arrived at the same conclusion. :-( I
> certainly don't want multiple table rows per path. Perhaps the answer

As with Bill, I'm not sure multiple rows is a problem.

> is to map
>
> revision-id => (path, node-revision-id)
>
> and populate the `changes' table rows for a given revision during the
> deltification walk post-commit.

I don't think that would be a good idea. The deltification walk might be
asynchronous at some point. If that happened, then there would be a race
between the commit and the completion of the CHANGES table. As long as it is
kept synchronous, it would work, and it would allow for a very compressed
CHANGES table.

I'm not quite sure about some of the various keying proposals, so I'll just
let you think more on it. Let us know what you figure out :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org