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

RE: svn commit: r1102843 - /subversion/trunk/subversion/libsvn_wc/wc-metadata.sql

From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 13 May 2011 23:06:22 -0700

The format 20 bump introduces a foreign key (now) which breaks upgrades
if you have md5 checksums.

When we originally bumped to 20 this constraint wasn't there yet (added
in January as 'small' change without impact.

danielsh reported a broken update caused by this change on IRC.

Bert Huijben (Cell phone) From: Greg Stein
Sent: zaterdag 14 mei 2011 7:13
To: dev_at_subversion.apache.org
Subject: Re: svn commit: r1102843
- /subversion/trunk/subversion/libsvn_wc/wc-metadata.sql
On Fri, May 13, 2011 at 14:13, <rhuijben_at_apache.org> wrote:
> Author: rhuijben
> Date: Fri May 13 18:13:06 2011
> New Revision: 1102843
> URL: http://svn.apache.org/viewvc?rev=1102843&view=rev
> Log:
> * subversion/libsvn_wc/wc-metadata.sql
>  (STMT_UPGRADE_TO_20): Following up on r1102837, update BASE_NODE and
>    WORKING_NODE instead of the empty (just created) NODES table.

As with my statement on r1102837, I recommend just dropping this.
There isn't any reason to do this for the f20 bump, since the f28 bump
will take care of it. And the upgrade process should run all those


Received on 2011-05-14 08:06:58 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.