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

Re: Status of fs-successor-ids

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Tue, 13 Sep 2011 21:42:12 +0300

C. Michael Pilato wrote on Tue, Sep 13, 2011 at 14:25:14 -0400:
> On 09/13/2011 02:04 PM, Daniel Shahaf wrote:
> > Does anyone have ideas for how to implement 'upgrade' for the BDB backend?
> The BDB situation should be about the easiest scenario possible. I mean,
> it's a database, for crying out loud. My not-completely-thought-out
> approach would be: run a cursor over the whole `nodes' table, reading
> node-revision-ids (the keys of that table) and precessor-ids (parsed from
> the values of that table), and store the reverse mapping in the `successors'
> table.

In other words, run over the noderev-to-predecessor mapping and reverse
it. No argument about /that/. But do we make 'svnadmin upgrade' do
that, or do we introduce a bit that says "Set this bit to '1' after
you've built the successors mapping"?
Received on 2011-09-13 20:43:48 CEST

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.