> [ and as Tutt noted at some point, storing a UUID a gazillion times across
> the DB gets expensive; thus, I figured that storing indices into a RECNO
> database would be good, with idx==0 being "self" ]
>
> [...]
Heh, I think we're being way premature here :-). We have no idea yet
how we're going to record cross-repository history; even if we do end
up using a new table that maps small numbers to UUIDs, *this*
repository's own UUID is still special, since it is the one handed out
as a source identifier for data coming from this repository. Just
stick it in a file in the top level and be done with it. If we end up
recording ancestries in a table, then this UUID can still be stored in
that table like any other (and we'll be better off for treating it
just like any other UUID, instead of depending on it being record
number 0 or whatever).
I don't think the "K.I.S.S." principle applies equally well in all
situations... But it's especially apt in situations like this one,
where one doesn't really know what one is going to do next.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 07:27:12 2003