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

RE: repository GUIDs

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-12-12 02:38:32 CET

> From: Branko Cibej [mailto:brane@xbc.nu]
> Yes. Changing a unique ID is always a bad idea. Ben, d'you think you
can
> make that one property read-only? I'm afraid it probably means adding
a
> rudimentary access-control mechanism for revision props.

While Brane makes a great comment about ACLs and revision properties,
I'd like to point out at the filesystem level that the best place to
stick this information is in a new BDB table. Even if you expose the new
table through the ra layers as a revision property, we're still further
ahead of the game if we add a new BDB table for this.

The new table is very simple. All it needs at the moment are two
columns:
RespositoryID and GUID. RepositoryID is just another one of our fun
monotonically increasing ID fields, and the GUID column is the
repository GUID. The reason for structuring the data this way is that
eventually we'll want to widen at least the NodeRevision primary key by
RepositoryID. We don't want to widen the NodeRevision PK by the
repository GUID mainly because GUIDs cluster so poorly on indices. No
need to waste valuable page &/or index space.

FYI,
Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 12 02:39:19 2002

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