[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Minimizing the `revisions' table.

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-06-14 22:55:27 CEST

> From: Greg Stein [mailto:gstein@lyra.org]
>
> On Fri, Jun 14, 2002 at 01:10:11PM -0700, Bill Tutt wrote:
> > > From: cmpilato@collab.net [mailto:cmpilato@collab.net]
> >...
> > > Oh, "replace = delete + add", where modify means "text or prop
> > > changes". Sorry for the ambiguitiy.
> >
> > Replace is unnecessary if the primary key of the table is:
> > (TxnID, NodeRevisionID)
>
> BDB doesn't do multi-column primary keys. Well, it *can*, but you
could
> not
> come along later and ask for all rows related to TxnID.
>

Duplicate keys + TxnID as the BDB key would work as well.
I mean we're only either inserting one row or returning all the rows
anyway right?

> >...
> > Let client applications detect replaces and renames. :)
>
> Yah.
>
> > Otherwise, if the key was (TxnID, Path) we'd need two
NodeRevisionIDs in
> > the skel. One for the deleted one, and one for the added one. (since
> > they have differing NodeIDs)
>
> Might be needed to get what we need, tho.
>
> Cheers,
> -g
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 14 22:55:55 2002

This is an archived mail posted to the Subversion Dev mailing list.