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

Re: Node origins cache rewrite

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 28 Jan 2008 13:17:34 -0500

David Glasser wrote:
> On Jan 25, 2008 12:50 PM, David Glasser <glasser_at_davidglasser.net> wrote:
>> On Jan 25, 2008 11:16 AM, David Glasser <glasser_at_davidglasser.net> wrote:
>>> On Jan 24, 2008 6:54 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>>>> I see David has rewritten this to no longer use SQLite. Yay!
>>> Here's an alternative implementation. In FSFS, at commit time, new
>>> node IDs are rewritten from a temporary value like "_ab3" to a unique
>>> value by adding "ab3" to the "start_node_id" field in the current
>>> file. This makes them not only unique, but also part of an ordered
>>> sequence without gaps.
>>>
>>> Is it actually important that node IDs be ordered and gapless? We
>>> could just change new node-IDs (in format 3 repositories) to be built
>>> as "<rev>-ab3". get-node-origin-rev would be trivial on these nodes.
>>> Pre-format-3 repositories, or nodes in format 3 repositories that
>>> aren't dumped and loaded, would require the slow crawl.
>> Like this. Can somebody review?
>
> New version, supporting "svnadmin recover". Barring objections, will
> commit later today.

I object. See other mails in the thread.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2008-01-28 19:17:47 CET

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.