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

Re: Repository UUID Implementation

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-01-09 07:00:21 CET

On Thu, Jan 09, 2003 at 12:50:56AM -0500, Greg Hudson wrote:
> On Thu, 2003-01-09 at 00:32, Greg Stein wrote:
> > Yup. I was thinking the same thing in the car earlier. A bit different than
> > your idea, tho. I was thinking of a RECNO database, with each record being a
> > UUID. Index 0 would the "self" UUID. The other indexes would represent UUIDs
> > of other repositories which participating in merges/copies into "self". This
> > would support the notion of recording copy/merge history like so:
> >
> > $ svn cp http://svn.apache.org/repos/asf/apr \
> > http://svn.collab.net/repos/svn/apr
> So, I don't really feel strongly about where we store UUIDs. But I
> don't want to see us designing a table designed to accomodate
> information about *other* repositories before we know that it's
> necessary and how it will be used.

Sure. In all likelihood, initially, the table will just contain a single row
and that'll be it. mbk's approach defined a "metadata" table; again, with
just a single value in it.

*shrug* Any approach is really going to be about storing a single value,
and we're only guessing about future uses. I just liked my forward vision
more than mbk's ;-)


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
Received on Thu Jan 9 06:59:12 2003

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.