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

Re: upgrade test failures

From: Branko Cibej <brane_at_xbc.nu>
Date: Sun, 19 Apr 2009 19:23:42 +0200

Greg Stein wrote:
> What if you just toss loggy from the upgrade story (for the v12
> upgrade, if possible; leaving it there for now for v11 upgrades). Or
> if you can't, then keep this in mind for the future.
> How about:
> 1) Port entries and property data into wc.db
> 2) Remove 'entries'
> 3) Remove all property files
> If an interruption happens at any point, this is detectable by
> 'entries' *and* 'wc.db' present in the subdirectory. When that
> happens, remove wc.db and start again.
> Oh, hmm. We don't want to have to stat for 'entries' every time we
> look in a .svn subdir, let alone stat around looking for un-removed
> prop files. Alrighty. There needs to be something in the database that
> will give us an indication of "in-process on upgrading; if you're
> seeing this, then it was interrupted; go investigate". Something in
> the format number? Maybe a temporary table whose presence/absence acts
> as a boolean?

I'm gonna put my foot in it and suggest that you create the wc.db as
not.wc.db, transfer entries and stuff, close the DB and rename the
database file ... nice and atomic.

-- Brane

Received on 2009-04-19 19:24:03 CEST

This is an archived mail posted to the Subversion Dev mailing list.