RE: Re: revision numbering (was: Re: Multiple projects in one repository!)
From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-05-04 16:43:36 CEST
Indeed, those long NodeRevisionIDs are why issues's 653 and 654 are
The new primary key for the "NodeReviosion" aka NodeChange table will be
Bill
---- Do you want a dangerous fugitive staying in your flat? No. Well, don't upset him and he'll be a nice fugitive staying in your flat. > -----Original Message----- > From: Glenn A. Thompson [mailto:gthompson@cdr.net] > Sent: Friday, May 03, 2002 11:15 PM > To: Subversion Dev list > Subject: Re: revision numbering (was: Re: Multiple projects in one > repository!) > > Ouch! My brain can't handle that. > > What series of events causes this? Is it branches that have nodes that > have > branches? > I'm playing with svnadmin lsrevs. This should help to get my brain > wrapped > around this stuff a little better. > If I know what commands I issued and have the state of the FS I think can > follow along in the code easier. > But this definitely creates some problems for a SQL DB. Yikes! > > Shit it's past 2 and my wife has a honey-do list a mile long for me. > > Have a good nite. > > gat > > cmpilato@collab.net wrote: > > > "Glenn A. Thompson" <gthompson@cdr.net> writes: > > > > > Something else that confused me: > > > > > > I was reading issues 653 and 654. > > > > > > I must confess I got stuck on the first sentence of 654. > > > "Right now, we use a representation for NodeRevIDs which is unbounded > in > > > length." > > > > > > I'm still trying to figure out how NodeRevIDs have unbounded length. > > > > > > So: > > > - "100" is a node id. > > > - "100.10" is a node revision id, referring to revision 10 of node 100. > > > - "100.10.3" is a node id, referring to the third branch based on > > > revision 10 of node 100. > > > - "100.10.3.4" is a node revision id, referring to revision 4 of > > > of the third branch from revision 10 of node 100. > > > And so on. > > > > > > Does this notation continue on like 100.10.3.4.1.1? > > > In looking at some code I thought it could only be the 100.10 or the > > > 100.10.3.4 case. I know I saw some code checking > > > for those two cases. I can't remember what for. > > > > This is precisely the problem. For example, the node revision for the > > trunk/ directory in our source code repository right now is: > > > > 1.35.1.192.2.157.1.380.1.28.1.87.1.40.1.109.4.5.3.102.5.3.2.131.\ > > 2.178.1.272.1.24.3.47 > > > > *Zoinks!* > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org > > For additional commands, e-mail: dev-help@subversion.tigris.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org > For additional commands, e-mail: dev-help@subversion.tigris.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Sat May 4 17:11:30 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.