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

Re: Making fsfs generate unique transaction names

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2007-06-18 21:19:58 CEST

On Mon, Jun 18, 2007 at 02:29:07PM -0400, C. Michael Pilato wrote:
> > I've seen the long transaction names in the transaction fsfs files, but
> > you're saying they also end up in revisions?
> Now, remember, I'm only talking about BDB here. In BDB, node-revision-IDs
> never change -- they begin life as NODE-ID.COPY-ID.TXN-ID (where TXN-ID is
> the name of the transaction), and they stay that way even after the
> transaction is promoted to revision-hood. I don't know if FSFS repositories
> have that same property or not.

I was going to say "no, they don't" - and they don't, for the most part
(the 'transaction id' part of an unmutable node is converted into an
"rN/offset"'transaction' upon commit). But I see that they do appear to
be used in the changes list at the end of the revision - I don't know if
that's important or not. (Or even if it's an oversight/bug, or if I'm
completely wrong - I'm a bit busy right now, sorry! :-))


  • application/pgp-signature attachment: stored
Received on Mon Jun 18 21:23:14 2007

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.