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

RE: Re: `svn log -v' time inefficiencies

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-06-13 23:32:48 CEST

> From: Branko Cibej [mailto:brane@xbc.nu]
>
> Greg Stein wrote:
>
> >Well, I'd also point out that if we had SQL, we'd just find the
changed
> >nodes using a simple query against the TXN_ID. Of course, that finds
the
> >*nodes*, but not the paths. (but that is a concern for another day)
> >
> >
> I distinctly remember talk about each NodeChange storing the path
under
> which it was committed. If we did that, we could look up the txn, then
> build the list of changed paths from the NodeChange records.
>

Given deletions the schema that comes to my mind is:
TXN_ID -> (NodeRevisionPK, Path, WasDeleted)

Where NodeRevisionPK and Path is obvious and WasDeleted would be a
boolean value.

Attaching it to the Repository Revision is incorrect, because the data
really belongs to the Transaction.

Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 13 23:33:25 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.