[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: Eric Gillespie <epg_at_pretzelnet.org>
Date: 2007-06-14 06:50:24 CEST

Blair Zajac <blair@orcaware.com> writes:

> After looking at this, I'm wondering if maybe we should use sqlite
> to store a sequence value in it and use the same key incrementing
> approach that the BDB backend uses to generate transaction names.
> The current value of this sequence would be dumped along with the
> repository and imported, thereby preventing the reuse of a
> transaction name. I believe that if you dump and load a BDB
> transaction, then currently, sequence is reset.

Jebus, i'm afraid fsfs is going to turn into a complete
hodge-podge. revs and revprops in one format, locks in another,
mergeinfo in a third (and this talk of "read locks" is *really*
scaring me; that's one hell of a regression!), and now two
proposals this week for *more* sqlite dbs: revprop indexing and
sequence values?

Color me -0.9 this one.

Eric Gillespie <*> epg@pretzelnet.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 14 06:50:33 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.