RE: Two svn_wc__db_t for single-db upgrade

> Back up a step. *What* data do you need to query? Maybe there is a
> more
> direct solution.
>
> I very much dislike a special mode for wc_db. It just screams
> "hack".
>
> On Aug 27, 2010 10:07 AM, "Philip Martin"
> <philip.martin_at_wandisco.com>
> wrote:
> > "Bert Huijben" <bert_at_qqmail.nl> writes:
> >
> >> I really think that it is much easier to just walk the entries
> files
> using
> >> an old style-lock, constructing a new sqlite db 'upgrade.db'
> somewhere
> >> outside the normal location using upgrade specific code.
> >
> > That might be another way to do it. If we construct a temporary
> 1.7
> > root within the 1.6 root, something like:
> >
> > .svn/tmp/qyh2h2n2/.svn/wc.db
> >
> > then we should be able to query that database by converting a
> path
> > /some/wc/A/B by to /some/wc/.svn/tmp/qyh2h2n2/A/B.
> >
> > --
> > Philip

I'm just talking as a user here... and not an svn dev... but do you really need to spend time on a 1.6 to 1.7 WC upgrade? Why not just have 1.7 not work with 1.7 WCs and tell the users they need to do a new checkout with 1.7. I mean... it might annoy some people, but I just think that the svn dev team would have "that much" more time to work on the real features/functionality of 1.7. I'm sure upgrades from WC-NG to WC-NG.Next will be much simpler and can/should still be included.

BOb
Received on 2010-08-27 18:03:42 CEST